How focused projects can be structured for what comes next
A project with a defined scope can still leave the door open. It takes a few deliberate choices from the first week, not a handover document written in the last.
What does it mean to structure a project for what comes next?
A focused project is structured for what comes next when it ends with more than its deliverables: clear decisions, documented reasoning, a system that others can extend, and a short list of what to evaluate after launch. That comes from choices made at the start and carried through the work, so whoever picks it up next, whether your team, us or another partner, begins from understanding rather than from scratch.
Focused Projects are one of the three ways we work, alongside Custom Solutions and Ongoing Partnerships. They suit a defined scope: a brand identity, a corporate website, a UX engagement, a reporting interface or a specific improvement. A defined scope is not a smaller standard. It simply means the project has a clear edge, and the edge deserves as much design as the centre.
Why ask about “next” at the start?
Most of what makes a project easy to continue is decided early, long before handover. So in Define & Explore, alongside the immediate objective, we ask a few questions about the future:
- What is likely to change in the next year or two: new services, markets, languages, people?
- Who will own this after launch, and what skills do they have?
- Which parts are expected to stay stable, and which will be revisited often?
- What would you want to evaluate once it is live?
The answers rarely change the scope. They change how things inside the scope are built. A website for one language today, with a second language likely later, is modelled differently from the start. A reporting interface that will gain new data sources is structured so that adding one does not mean redesigning the screen.
Build things that can be extended
Extendable work tends to share a few qualities, whatever the discipline:
- Systems rather than one-offs. A small set of reusable components, styles or templates, named and documented, rather than a collection of individually crafted pages.
- Clear naming. Files, layers, content types and code follow conventions a newcomer can understand without a guide.
- Content separated from presentation. Editors can change what is said without breaking how it looks, and designers can refine how it looks without rewriting what is said.
- Ownership in your name. Domains, hosting, design files, repositories and analytics accounts belong to your organization, with access you control.
None of this is gold-plating. It is usually the same amount of work done in a more considered order.
We design for what comes next, not just what goes live.
Efabrika
Document decisions, not only deliverables
A finished design shows what was decided. It rarely shows why, or what was considered and set aside. That reasoning is what the next person needs most, and it is the first thing to be lost.
We keep a short decision record throughout Design & Develop: the question, the options we looked at, what we chose and the assumption behind it. It is a working document, not a report. At the end it sits alongside the deliverables, together with open questions we did not resolve within the scope, and the reasons they matter.
Leave a clear starting point for Optimize
Not every client chooses ongoing optimization, and a focused project should not presume it. It can still make improvement easy to begin. Before handover, we agree on:
- what to observe once the work is in use, and where that information will come from
- the questions that only real use can answer
- a sensible moment to look again, and who will do it
This turns Optimize from an abstract intention into a short, practical plan your team can run on its own, or with us.
Moving between ways of working
A well-structured focused project gives you real choices afterwards. You might take the work in-house with a clean handover. You might return with a new Focused Project when the next need is clear. You might move into an Ongoing Partnership for product evolution or creative production, or into a Custom Solution when the next challenge is broader and less defined. Each route is equally valid, and none should be forced by the way the first project was built.
Continuity, for us, means keeping context, knowledge and improvement across time. Sometimes that is a long partnership; sometimes it is a handover clear enough that the next step is easy.
If you have a focused piece of work in mind, our Approach page explains the three ways we work, or you can tell us about it.