UX for non-designers.
A one-day in-house programme for engineers, product managers, analysts and ops people who already make design decisions without the title. Run on your own product.
A decade of design training. Companies that have paid us to train their people.
The people deciding design by accident.
Most products are shaped by people who were never trained to shape them. This day gives those people a method instead of an instinct.
Engineers, PMs, analysts and ops
Making design decisions without the job title.
No designer, or one with a queue
Teams who have never worked with a designer, or have one and a long wait.
AI tools arrived first
Before anyone agreed how they should be used.
Asked to make it user friendly
With no method behind the request.
Six things that stop the guessing.
Run against one real feature of yours, not a hypothetical one.
What a designer actually does, and what you can do yourself
Separate the parts that need a specialist from the parts your team is already deciding by accident.
→ a line drawn between what you keep and what you hand overFinding out what users need without a research team
Five conversations, run properly, beat a survey nobody acts on. We run one in the room.
→ a short interview guide your team can reuseThe assumptions you are treating as facts
Write down what the team believes about its users, then sort it into known, guessed and never checked.
→ your assumptions sorted, with the riskiest ones namedStructuring a flow before anyone opens Figma
Sketching, naming the steps, and arguing about the shape of the thing while it is still cheap to change.
→ a sketched flow for one real feature of yoursWhere AI genuinely helps, and where it will mislead you
Synthesis, first drafts and variations are fair game. Deciding what users want is not.
→ prompts that worked, and a list of what to stop asking itTesting something small before you build it
Put a sketch in front of five people, watch what happens, and change your mind cheaply.
→ a test you can run next week without hiring anyoneArtefacts, not just a good day out.
A sketched flow
For one real feature, made by the people who will build it.
Assumptions, written down
Sorted into known, guessed and never checked.
An interview guide and test plan
You can run it next week without a researcher.
Shared vocabulary
So design reviews stop being arguments about taste.
Before you enquire.
Do people need any design experience?
None. The day assumes no design background at all. It is built for people whose job is something else and who keep running into design decisions anyway.
Will this turn our engineers into designers?
No, and we would not claim it. One day gives a team a shared method and enough research skill to stop guessing. It does not replace hiring a designer, and where a problem needs one we will say so on the day.
Do you use our product, or a worked example?
Yours. We ask for one real feature or flow in advance and build the day around it, so what the team sketches and tests is work they are actually doing.
How is this different from your beginner course?
Have you taught non-designers before?
Enquire about this programme.
Tell us who would be in the room, the feature you want to work on, and your preferred timing. Naveed will reply personally within one working day.
*Advertised price assumes 10 or more participants. Prices vary depending on the number of participants.