Every so often someone asks me, “So, have we got the green light for Project Blah?” There is always some project that’s particularly exciting, and anticipated by team members, and … Continue reading You don’t need just one green light for a project
A short time ago a friend brought up the subject of project code names. On the one hand, he thought they might be useful for team bonding (“We’re project Dolphin!”). … Continue reading Some thoughts on project code names
I’ve written before about the importance of having a value statement for a project or programme. This is a clear statement of the value we’re supposed to be delivering, and … Continue reading Creating a sequence of value statements
The other week someone introduced me to the idea of “input goals” and “output goals”, by Oz Chen. Oz writes about “personal development and content strategy”, so his purpose in … Continue reading Input goals and output goals
I often talk to people about their “value statement”—a statement of the value of their programme or project. But how do we make our value statement most effective? From my … Continue reading What makes a good value statement?
When things get confusing I always rely on a handy model, image or diagram to clarify things. So it was often frustruting for me when, in the early days of … Continue reading Separating risks and issues (or not…)
Is there a simple way to ensure a programme of work gets off on the right foot? Sometimes I’m deep within a such programme—it’s already in full swing and it’s … Continue reading There is only one conversation in a programme