How well does the team understand the problem we are trying to solve? Can we quantify the issue? Do we understand the systems—both technical and organizational—that contribute to the problem?

If we can’t answer these questions clearly, this is the place to start.

Do we know who is involved in the process we’re interested in changing? Do we know what they do? Who they answer to? What they struggle with? What tools they use to do their work? What they like and don’t like about their jobs?

If can’t answer these questions? It’s a good place to start.

When engaging with a complex system or organization—especially if your product is early stage—it’s critical to identify the levers you’re trying to pull. Where can you intervene and start demonstrating value early.

We’re all fond of saying it, but let’s do it again for good measure… Don’t boil the ocean.

If we know the problem and the people involved, do we know what change we are looking to make? Can we quantify success? Do we know how we’d measure it?

If we can’t answer these questions… you know we’ve got to start here.

My favorite part. How are we going to start testing the assumptions we’ve laid out. What can we do quickly to shed greater light on all the categories above?

Build something + test it with users. Don’t ask. Show. And then refine it all.