Redefining Success: Start With the Outcome, Not the Activity

Activity can create the appearance of progress. Meetings are scheduled. Requirements are documented. Tasks are assigned. Status reports are produced. Everyone is busy.

But a full calendar and a long task list do not necessarily mean an organization is moving closer to the outcome it set out to achieve.

One of the most important questions at the beginning of any initiative is also one of the simplest:

What does success actually look like?

That question changes the conversation.

Instead of beginning with What do we need to do?, teams begin with What are we trying to accomplish? Once the desired outcome is clear, the work can be evaluated against it. Requirements become easier to prioritize. Processes can be challenged rather than simply replicated. Technology decisions have context. And stakeholders have a common reference point when competing priorities inevitably emerge.

Activity Is Not the Same as Progress

Complex initiatives naturally generate activity. Workshops, discovery sessions, documentation, design discussions, testing, approvals, implementation plans — all of these may be necessary.

The problem comes when completing those activities becomes the definition of success.

A requirements document can be completed without solving the right problem. A new system can be implemented without improving the underlying process. A project can meet its milestones and still leave the organization wondering whether anything meaningful actually changed.

The work matters. But the work should always serve the outcome.

Start With the Problem

Before designing the solution, understand the problem well enough to explain it clearly.

What is happening today? Where is the friction? Who is affected? What constraints are real? Which assumptions need to be tested? And perhaps most importantly, what should be different when the work is complete?

Those questions create something every complex initiative needs: clarity.

Clarity doesn't eliminate complexity. It gives people a shared way to navigate it.

Define Success Before You Measure It

Success should be more specific than “implementation complete.”

Depending on the initiative, success might mean fewer manual handoffs, clearer accountability, faster processing, improved visibility, reduced operational risk, a better customer experience, or simply enabling people to do their work more effectively.

The measures will differ. The principle does not:

Define the outcome first. Then determine the work required to reach it.

That creates a much stronger connection between strategy and execution — and makes it easier to recognize when activity is no longer contributing to meaningful progress.

A Better Question

When an initiative becomes complicated, the instinct is often to ask:

What do we need to do next?

Sometimes the better question is:

What outcome are we trying to create — and is what we're doing actually moving us toward it?

That small shift in perspective can change priorities, conversations, and ultimately results.

Because meaningful progress isn't measured by how much work gets done.

It's measured by whether the work moves something that matters.