Bring design in before the requirements are written
Ask a bank design leader where design problems start and you rarely hear about screens. You hear about the problem statement, the requirements and the planning that happened before design was in the room.
Design is often brought in too late, and asked only to make the screens. This guide is for Heads of Digital and design leaders who want design in discovery without a reorg.

What "too late" looks like
A request reaches design with a deadline and a feature name. The strategy does not quite match the problem it is meant to solve. Key requirements are missing. The designer has two choices: guess, or wait.
Either way the cost shows up later. Screens come back from legal or accessibility review. Product changes direction after the first build. The team redesigns work it already finished, and design looks slow when the real delay sat upstream.
Why it keeps happening in banks
Banks are full of alignment meetings because requirements and processes change often. A design team that supports many business lines gets requests from all of them, and each one arrives as the top priority.
In many banks design now reports into product. Product decides what gets built, and design is asked to execute. That makes it easy to treat design as the team that makes screens, not a partner that shapes the problem.
Over time the system teaches people to wait for a ticket. Designers who started out pushing new ideas learn how hard change is inside a bank, and some become the first to explain why something can't be done. That is not a talent problem. It is what late involvement trains people to do.
What changes when design is in discovery
- The problem gets sized before the screens. When design hears the problem statement early, the team can plan the design capacity it will need instead of discovering the scope mid-sprint.
- Review surprises move earlier. Accessibility and regulated content get checked while the work is still a sketch, not the week before release.
- Requirements become something designers can work from. Good business analysts turn requirements into inputs a designer can use. Design in the room makes that translation part of the work, not a later fix.
- Design argues from the business case. A designer who knows the goal can defend a choice in terms the business owner cares about.
How to get design in earlier without a reorg
1. Start from next year's plan. Large initiatives at a bank are usually known months ahead. Pick one and name a designer before requirements are written.
2. Invite design to problem framing. One working session with product, the business owner and a designer is enough to start.
3. Write a one-page problem brief. Who is the customer, what is broken, what measure should move, and what is out of scope.
4. Ask the business-case questions out loud. Why this, why now, and how will we know it worked.
5. Book the reviewers early. Put legal, compliance and accessibility on the calendar at the sketch stage, not at the end.
Where an embedded squad fits
Most in-house design leads would like to spend more time upstream. They can't, because the production queue never empties. An embedded squad takes on production load under your leads, which frees those leads for discovery and problem framing.
A squad does not own your requirements or your priorities. Product and the business still decide what comes first, and the squad works inside your process. What a good squad brings is the habit of asking why the work exists, and what business case it is meant to serve.
Quick answers
Why is design brought in too late at banks?
Planning and requirements often happen before design is invited, and design is seen as the team that makes screens. Many business lines compete for the same design team, so requests arrive as finished asks.
What should a designer do in discovery?
Help frame the problem, size the design work, flag accessibility and content risks early, and turn the business goal into something the team can test.
Does an outside design team replace product discovery?
No. Your product and business owners keep ownership. An embedded squad adds capacity so your own design leads have time to take part in discovery.