AIM Framework, Step 1: Align on Who, What Outcome and Why
Stay up to date with the latest insights
A while ago, I wrote about the AIM framework as a way to connect company strategy to product work in three steps: Align, Identify, and Measure. You asked for more details, so here we go.

Over the next three newsletters, I’ll break down what each step requires from product teams and from leadership. I’ll use the same example throughout - my time at Doodle, so you can see how the three steps connect in practice.
Even if Align isn’t where you’re stuck right now, it’s worth understanding this first step. The three steps build on each other, and the other two won’t make much sense without understanding what alignment is supposed to achieve.
Aligning is not the same as stating a goal
One of the most common mistakes I see in organisations is assuming that aligning with the product team simply means communicating the company goals.
Let me show you why this is wrong.
Imagine leadership tells the company that the goal is to "increase revenue by 20% this year." That's a SMART goal - Specific, Measurable, Achievable, Relevant, Time-bound. But it doesn't tell a product team in which way to achieve it. It just generates a whole stream of questions: Increase revenue how? By selling more to existing customers, or entering a new market? By growing subscription revenue, or advertising revenue?

Those are different strategic choices, and they lead to different problems for a product team to solve. So before a team can start working, there needs to be another layer of thinking between the company goal and the work itself.
For me, alignment starts with understanding who we’re trying to solve a problem for and what we want to achieve, both for them and for the business. Then, we also need to agree on how we intend to approach the problem, by when, who needs to be involved, and how we’ll know we’ve succeeded.
These questions give the team a shared direction. Depending on your company, your stage, and your leadership, alignment can look very different in practice.
Five ways alignment can look in practice
Alignment can take many forms, but its function is always the same: give teams a clear problem to solve and enough context to understand what they’re trying to achieve and why.
Below are five common patterns, from “ideal” to “bare minimum,” and what to do in each.

Metrics Trees
In the best-case scenario, alignment is explicit. Let’s be clear: there is no perfect world in which alignment is perfectly explicit, and everybody is on the same page. But there are some helpful methods. A Metrics Tree can make the connection between different metrics and the business goal visible, helping teams understand how their work contributes to the bigger picture. Impact Mapping can complement this by connecting a specific actor to the outcomes we want to create for them, and linking those outcomes back to the business goal. With this, a team can see three things at a glance: who they’re serving, what outcome matters to that actor, and how that outcome ladders up to the business goal.
This is already a high degree of alignment, and it’s also the one that demands a lot from leadership. It requires leaders to do the hard work of turning a company goal into a clearer direction for the product team. But this doesn’t mean leadership needs to have all the answers upfront.
Alignment on these points is a collaborative process between leadership and the product team. Leadership brings the business context, strategic priorities, and any non-negotiables. The product team brings its knowledge of customers, the market, and the product, along with questions and suggestions about how to turn that direction into something actionable.
Together, they need to establish:
The who (the segment or actor)
The business goal
The problem that needs to be solved for that actor
The timeline for achieving those goals
The value proposition
The research or reasoning behind those choices

Sometimes, the research doesn't exist yet, and that's fine. In that case, be explicit about it, don’t pretend you have certainty when you don’t. And other times, especially at very strategic levels, research happens more in the form of compound knowledge of different perspectives, earned through years of learning in the company.
Leadership is greatly responsible for the team’s trajectory. If you don’t give enough context, you’re setting them up to fail before they’ve even started working. Think about how you use AI: the quality of the output depends on the quality of the prompt. We just forget to apply the same standard to human beings.
On the team side, once the context is there, their job is to use it: ask clarifying questions, surface risky assumptions, and translate the direction into concrete problems, experiments, and roadmaps. They should also make suggestions when they discover that the underlying assumptions are weak or that the strategy doesn’t hold up in practice.
Scrappier, but still workable
In most early-stage startups, I’d be very surprised if there was a metrics tree for alignment. More often, alignment is something that lives in a founder’s head and ends up as a few pages on Confluence describing who the target group is, what problem they have, and why solving it matters for the business.
It’s less structured, but it can still do the essential job: give the team a clear who and a clear problem to solve.
In these environments, the test of alignment is simple: can everyone on the team explain, in their own words, who they’re serving, what problem they’re solving, and why this is the direction the company has chosen?
A bare goal
Sometimes, all teams get is a SMART business goal, like “increase revenue by 20%”. As mentioned above, this is simply too big for any one team to prove its work moved the needle, and it doesn’t say which strategic path to take.
If this is what you’ve been given, your job as a PM is to uncover the missing layers. Work with leadership to understand the strategic thinking behind the goal and what it means for your team. What assumptions are you making about how your work will contribute to the business outcome? What evidence supports those assumptions, and what still needs to be tested?
These “details” are the strategy. Different answers lead to different directions, and the team needs to work through the unknowns before committing to a solution. That doesn't mean waiting for all the answers before getting started. Explore the problem, ask questions, and run experiments to test your assumptions. If leadership can’t or won’t answer, treat that as data: you’re operating with incomplete alignment. Make your own assumptions explicit (“We’re assuming we’re focusing on X, because Y”), so you can test them later and adjust when evidence arrives. Once you understand the problem well enough, start building a solution, don’t wait for more data. The solution itself then becomes the experiment that qualifies the problem itself and the problem-solution-fit.
Just “ship it”
In many cases, you get none of the above. You’re simply told to ship something.
If that's your reality, treat "ship it" as the alignment. You've been told what to build, and that's your goal. If it later turns out to be the wrong call, you can point back and say, “we agreed I'd ship this, and I did.” Is this ideal? No. Would we like to change that? Yes. But first and foremost, you need to stay realistic and see if it’s the right place to push a change. If no, then stick to what’s been agreed on - or change your job.
But if you have some room to push, don't stop there. Go to whoever handed you the task and reverse-engineer it. Ask who it is for, what outcome they’re after, why it matters to the business, when it needs to land, and how you will know it worked. Reverse Impact Mapping, essentially. I wrote about it here and here. Worst case, you land exactly where you started, but aligned. Best case, you find a better solution than the one you were handed.
One important reminder: only do this if you have the psychological safety to question upward. Not everyone is in a position to challenge their manager or stakeholders.
Nothing to push on: build a “bubble strategy”
Sometimes there isn’t even a goal to reverse-engineer. The strategy hasn’t been communicated, or it’s so broad it doesn’t help (“grow the business”, “scale the platform”, “improve the experience”).
If that’s your case, build what I call a bubble strategy: a smaller strategic space your team defines for itself, then brings back to leadership for a decision. The bubble is not a way to bypass leadership; it’s a way to force the conversation leadership hasn’t had with you.
The simple version: pick your own strategic measurement point, and check if it's acceptable to your product leader. For example, “If adoption of this new feature is high among target segment X, we believe it will contribute to the broader goal.”
The more complex version starts from almost nothing and builds a mini-strategy inside your bubble:
Start from your team’s mandate or reason to exist (for example, “serve businesses, not consumers”)
Choose a specific slice of that market to explore (SMB, freelancer, enterprise, or even more precise, like “event organisers who handle participant booking”).
Talk to people in that segment about their pains, gains, and jobs to be done, and map the real competitive set (including the status quo).
Identify gaps that could be worth solving, design small experiments to test your hypotheses, and bring the resulting narrative back to leadership for a decision.
The Doodle example
At Doodle, the company was historically funded mostly by advertising on the free version of the product. There were subscription tiers, but hardly anyone used them.
The strategic goal was to change that: grow subscription revenue and move towards a 50/50 balance between advertising and subscription revenue within three to four years, letting ad revenue keep growing modestly in the meantime, without it being the focus.
That’s far more specific than “increase revenue,” but it still wasn’t a product goal. “Increase revenue” is a company goal. “Move to a 50/50 ad‑to‑subscription mix” is a strategic choice. Neither one tells a team what to build.
To make that direction more actionable, we identified further strategic opportunities and developed a strategic roadmap around them:
Improve the checkout and subscription management experience.
Make polling more relevant and useful in our target group’s business context.
Make the paid tiers more valuable to attract premium customers and create demand for paid subscriptions.
Make Doodle more relevant in business contexts.

These choices gave us more direction than the revenue target alone. My group’s focus was to increase the value of the subscription tiers themselves, but for a brand-new product like Doodle 1:1, there was no way to directly attribute subscription conversions to it. So we built a bubble: we agreed with my CPO that if adoption of the new product was high and we’d crack activation, we’d treat that as evidence it was contributing to tier value. Once he signed off on that belief, it became our working strategy.
My group and I didn’t get there by chance. Starting from almost nothing beyond “grow subscription revenue to 50/50,” we went back to our mandate: we existed to serve businesses, not individuals. From there, we chose a slice of that market to explore, talked to people about their pains, gains, and jobs to be done, and mapped the real competitive set (at the time, mostly Calendly plus email and spreadsheets). Plus we had to deprecate Doodle Meetme, but its heavy users loved it. That led us to Doodle 1:1 and Bookable Calendars (now Booking Pages) as the bets worth making, and adoption & activation as the proxies we’d measure it by, which we then took back to our CPO for sign-off.
Conclusion
Alignment is an ongoing agreement about what problem the team is solving, for whom, and why it matters. When alignment is strong, teams can argue about priorities without arguing about purpose. When it’s weak, every decision becomes a negotiation, and energy drains into politics instead of progress.
As a leader, your job is to give teams a problem worth solving and enough context to make good bets. As a product manager, your job is to use that context to ask better questions, make assumptions visible, make suggestions, and, when necessary, build a bubble that forces the missing conversation.
Whatever form alignment takes in your organisation, ask these questions to check if you have a shared understanding:

Who are we trying to solve a problem for?
In which way are we trying to help them?
By when?
Who needs to be involved?
What do we expect to achieve for them and for the business?
How will we know we’ve achieved it?
In the next article, we’ll move into Identify: how to check whether the outcome you’ve aligned on actually holds, how to discover which opportunities are worth pursuing, and how to turn those opportunities into solutions that fit both the problem and the business.
This article is part of a four-part series on the AIM Framework:
The AIM Framework: Taming the messy middle between strategy and delivery
AIM Framework: Align - Who, what outcome, and why
AIM Framework: Identify - The right problem, the right solution (to be published)
AIM Framework: Measure - Make your bets testable (to be published)
—
This article was edited by Diana Bernardo.
Product management insights, delivered to your inbox
Sign up for weekly product insights. No spam.