How human beings Frame projects will change as teams use more AI-assisted tools. For example, if they enable the rapid generation of many options, you may decide to explore a broader range of concepts than before.
See the box at the foot of this article for further discussion on Framing.
A structure for Frames and Goals
Once the problem has been accurately diagnosed and an ambition and angle of attack agreed upon, the next job is to outline some endpoints to the project in the form of Goals. It’s these Goals that define the size and shape of the project and are often heavily influenced by budget and time frame considerations.
Discussing Goals is central to driving clarity at the start of a project, but this is best done around some clearly articulated draft Goals. If the discussion is too free-flowing, and is only recorded on a few quickly scrawled Post-its, the risk of blindspots and misunderstandings is high – even when everyone leaves the room nodding in agreement and raring to go.
Over three decades and hundreds of projects, I’ve developed the following way of structuring Frames and Goals.

I organise this under the following headings:
Context
Written out in a few paragraphs, this is where most of the framing happens. The paragraphs should outline the key elements of the challenge’s background. They should cover the broad business context, important drivers, why the project is being initiated and the assumptions, mental models and metaphors you consider helpful.
Those few summary paragraphs should be pithy and to the point, enabling the team and stakeholders to quickly grasp the project’s ‘why’. This is why using paragraphs is important here. Bullet points just don’t cut it when building a coherent narrative on your point of view on the challenge and how best to approach it.
Ambition
It’s always useful to distil the purpose of the project down into a single sentence. It should be concise and concrete without sounding like a vague wish. To find the right balance between brevity and detail, I typically generate a bunch of variants and, through discussion and iteration, narrow them down to the best statement of ambition.
Scope
This is where we break down different aspects of the challenge into various dimensions, such as: target market segments and geographies, product categories, use domains, touchpoints, business units, and time horizon etc. Often, it’s enough to outline what is in-scope, but sometimes, it’s necessary to clarify which elements of each dimension are out-of-scope.
Objectives
Written statements on each Objective break down the Ambition into the more specific Goals that, when achieved, will see that Ambition fulfilled. We find it helpful to start each Objective statement with a verb such as: Frame, Discover, Generate, Develop, Recommend, and to align these objectives with process steps. The statements should describe what you aim to achieve – not what you will do. For example, ‘Identify three potential disruptions in our market landscape’, not ‘Analyse market trends’. Finally, try to keep the number of Objectives down to between three and five – teams glaze over at the sight of a shopping list of Objectives.
The very act of writing what we think is clear in our heads usually highlights a few holes – then discussing them tends to highlight a few more.
Outcomes
If Objectives are the hard project Goals, Outcomes are the softer, often more important ones. Written statements of Outcomes highlight the desired consequence or impact of the project, and often describe the shifts in attitudes, mindsets and behaviour that will hopefully drive business results. Sometimes known as success criteria, they portray what success will look and feel like.
A good question to ask a client or senior manager is to imagine you’re sitting together in two years’ time: they’re happy, and you’re reminiscing about the project. What changed as a result of the project? What happened along the way to bring about these changes? Encourage them to think about the impacts on themselves, on their team, and on the business.
Three examples of Outcome statements:
- The executive team have had their eyes opened and their assumptions positively challenged
- The leadership team has developed and aligned around a point of view on which categories to play in
- The team feels confident that it has at least one compelling proposition which has the potential to generate high-margin growth
Outputs
These are the specific and tangible ‘deliverables’ the project will produce, as either intermediate or final outputs. They should be as specific as possible to help you clarify with your client or your manager that these Outputs match their expectations. Clear Outputs help you plan the time, resources and budget required to produce them. Examples may include:
- One slide of recommendations
- Agenda for a two-day workshop, including facilitation and summary
- 40-slide Foresight presentation
- Presentation and half-day workshop in Seoul
- Three digital prototypes as stimuli for consumer feedback
Iterate and align
Writing down and aligning teams and stakeholders on project Frames and Goals is time well spent. After all, writing is God’s way of telling us how muddled our thinking is! So, the very act of writing what we think is clear in our heads usually highlights a few holes – then discussing them tends to highlight a few more.
It’s the discussion of goals and their collective crafting that brings clarity, rather than the Goals themselves. Talking it through a few times with the team and stakeholders also helps hone a project’s narrative and iron out inconsistencies.
Once aligned at project kick-off, the Goals should be made accessible in the team’s workspace so that they can easily be referred to as a touchstone for the rest of the project. Whenever I suspect the team is getting stuck in the weeds, I refer to the Goals and ask if and how the current debate is helping us achieve them.
Mid-course correction
Often, the process of reflecting on the Goals mid-way through a project highlights subtle shifts in the team’s understanding of them. As the management thinker, Jon Kay put it: