Starting a New Project

Any new effort is an attempt at devising a solution to some problem or question. I think the solution - or at least the path to finding one - depends on properly defining the problem and asking the right starting questions.

Consider: a child tells a parent “I’m hungry.” After a series of “What about…?” volleys, the parent stumbles on the actual desire: the child wants ice cream and isn’t really hungry, but knows a meal precedes dessert.

Maybe the child was being intentionally circuitous. But while we may have intuitions about our goals, we sometimes have trouble articulating them.

For a project, if I can define the goals, risks, constraints, status quo, gaps, and distractions (i.e., a Strategy Bridge), solutions can become clear - viable options exist in the sometimes-limited space between those considerations.

So for a new project, I go through three steps:

Step 1: Define the Problem

Do a Strategy Bridge. If that doesn’t reveal a solution, apply these principles as you consider the problem:

This drafts a solution hypothesis.

Step 2: Build a Knowledge Base

Draft the following:

North Stars
Lists for What/Why vs How and Essential/Incidental/Noise (if not done already)
Backlog
Watchlist
Mind Map
Journal

This effectively starts a knowledge base for the project.

Step 3: Execute and Iterate

Work through the backlog (use IPMs, etc.)
Evaluate and refine: watchlists, backlog, etc.
Iterate

Step 3 is doing your process. Evolve your approach and converge on the needed outcome - which may not be the one you originally intended.