|
|
|
|
|
by attackroll
1535 days ago
|
|
Be clear about what problem your project solves. Strive to keep that problem statement small, focused on the highest ROI problem. Break the project down into milestones. That will tell you what to work on, and what not to work on. Set achievable deadlines to keep yourself accountable and laser focused on forward progress. If a bikeshed question arises, ask whether it can be deferred and easily changed later. If so, defe9r it. If the bikeshed question cannot be deferred, build consensus with the _key_ stakeholders. Try to keep that set of people small (just those with relevant expertise, and those with authority) and don't worry about pleasing everyone, trying that will be wasteful. Don't worry about the outcome, if its a small part of the overall ROI. Projects don't have to solve all problems, just effectively improve the status quo. |
|