LEADERSHIP
Leadership
Leadership
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
82 • <strong>LEADERSHIP</strong><br />
you’ve arrived at this chapter without a solid list of tasks and<br />
milestones, STOP! Now is no time to be jumping off the roof!<br />
Go back and build consensus around an approach and its required<br />
activities and actions. Remember, every outcome from<br />
this point forward is based on the quality of the WBS: bad list<br />
= bad plan = bad results.<br />
It’s easy to move forward with the wrong WBS—we can all<br />
be blindsided. Everyone can fall victim to the proverbial “unknown<br />
unknowns." And once you’ve made the leap into implementation,<br />
changing trajectories mid-air isn’t always an<br />
option. That takes superpowers you’ll find only in Marvel<br />
Comics. For now, I’m moving our planning discussion forward<br />
with the assumption that either you have a good task list<br />
(created by the people who will be doing the work) or you’ll<br />
build one before taking this next step: creating the schedule.<br />
I know you're ready to jump into this project and get<br />
things moving as quickly as possible, but before you leap,<br />
make sure all everyone team members on your team knows<br />
their roles and is are committed to their responsibilities. The<br />
work breakdown structure process has given you and the core<br />
team members a pretty good idea of who's going to be doing<br />
what, but at this point you need to get specific: exactly who, is<br />
going to do exactly what, exactly when. Getting specific about<br />
roles and responsibilities is the leader's job. Don’t ignore this<br />
simple but essential step: make sure all team members know<br />
their roles, responsibilities, and timeline of results. Facilitating<br />
Clarity of Action helps leaders reinforce Purpose and nurture<br />
their team members’’ Enthusiasm.<br />
In small-project environments and where team members<br />
frequently work together, a little additional planning and<br />
communication ado may be necessary to keep everyone in