Which people should join our creative team?

A creative team should include designers and developers from the start, with writers, strategists and client stakeholders involved when their knowledge shapes the decision. Designers bring the experience to life, developers test what can be built, writers shape the content, strategy grounds the work in the challenge, and clients provide business context. The right mix depends on the work, not on filling every meeting with every function.

Can developers improve a design rather than only flag limitations?

Developers can improve a design by identifying new technical possibilities as well as practical constraints. Their perspective can help a team account for accessibility, different devices and input methods before those details become expensive problems. The strongest designer-developer collaboration treats limitations as shared challenges to solve.

How should client stakeholders take part in creative development?

Client stakeholders should contribute throughout the creative process, especially where business knowledge, organisational context and feedback can sharpen the work. A partnership works better than occasional stage-gate presentations, but it still needs clear boundaries around who gives input and who makes final decisions. Ongoing involvement can make the process tighter when participants treat the work as a shared journey.

Should designers stay involved during development?

Designers should stay involved during development to help ensure the agreed experience is executed properly. Continued collaboration also helps designers understand technical choices that can improve future design work. Inclusion is easier to build into the process than retrofit once deadlines are tight.

When should developers join before designs are signed off?

Bring developers in while ideas can still change

Developers belong in the design process from discovery, before concepts harden and well before client sign-off. Early involvement gives a creative team a clear view of technical feasibility while there is still room to shape the idea. A developer can spot implementation constraints, identify edge cases and suggest possibilities that make an experience stronger, not simply smaller. That can mean checking colour contrast, planning for mouse, touch and keyboard inputs, or making sure a design works across different devices. A finished visual is a poor moment to discover that a key interaction cannot be built as intended. Designer-developer collaboration works best as a shared problem-solving process, with both disciplines able to influence the work before approval.

Sources: Designing and developing web experiences for everyone, No creator is an island

Build a multidisciplinary team around the decisions that matter

A cross-functional creative team is strongest when each person brings knowledge needed to make the work useful, feasible and clear. For digital brand and marketing work, pair designers with developers from the start, add writers when content shapes the experience, and involve strategy where the brief, audience insight or proposition needs defining. Client stakeholders should also contribute the business context that an external creative team cannot know alone. The point is not to invite everyone to every meeting. It is to bring the right people into the moments where their expertise can change the outcome. Give the team shared goals, clear roles and decision rights, so creative discussion produces progress rather than more rounds of review.

Sources: No creator is an island, Where logic meets magic: why strategy underpins every great idea, How to Turn Insights into Great Creative, Clients want people-led problem solving, not a list of services

Protect creative momentum with clear boundaries

Early collaboration pays off only when the team can make decisions. Give developers a defined opportunity to challenge technical feasibility before approval, while keeping a named creative lead responsible for the final idea. Bring client stakeholders in for business context and feedback, not as a rolling approval committee. Agree what is being decided, who decides it and which constraints are non-negotiable before workshops or reviews begin. That protects the value of co-design: more useful knowledge without turning every choice into a negotiation. When a project has no digital implementation need, or when a design is already fixed, adding a full developer role can create coordination cost without changing the outcome. The aim is useful integration, not a crowded room.

Sources: Clients want people-led problem solving, not a list of services, How to Turn Insights into Great Creative

Build feasibility into the idea, not the handoff

We believe developers should be in the room before sign-off because digital ideas must be ambitious and buildable. We involve developers in design from the beginning, where they can spot technical limits, suggest broader possibilities and make inclusion part of the work rather than a retrofit. On This is IBM, a developer helped confirm what was practical to implement while considering colour contrast, devices and input methods. On Dematic, strategy identified the need for an interactive tool, then designers and developers worked out how to bring it to life. That is the standard we back: shared problem-solving early enough to improve the idea, not merely approve it.