The brief
Draftboard is a concept: an AI builder that turns a prompt into a working internal tool. I wrote the brief as if from a client (the client is fictional). The problem: people love the first result, then lose trust when a follow-up prompt quietly rewrites screens they were happy with.
The goal: keep the speed of AI generation, but give people the control they get from code review, without asking them to read code.
Assumptions I designed against (not measured)
What I owned
- Framing the problem and the assumptions above
- Information architecture and flows for the builder, mobile app and website
- All UI, the design system and the motion
- The working prototypes on this page, built in HTML and JavaScript
Honest constraints
- Solo concept project with a fictional client, so no real users, PM or engineers. In a real team I would check feasibility with engineering at each decision below.
- No AI model behind the demo. Results follow a script, so I designed the states around the model, not its quality.
- The main users are not developers, so code cannot be the main way to build trust.
- Credits cost real money, so cost has to be visible before anyone spends it.
Planned timeline for this concept
About 6 weeks, split into five phases. This is how I would plan the work as a real engagement, not a record of time spent.
- Week 1DiscoverThe brief, the assumptions and two proto-personas
- Week 2DesignBuilder layout and the change review flow
- Weeks 3 to 4PrototypeWorking builder, mobile review app and website
- Week 5BuildDesign system, failure states and accessibility pass
- Week 6Test and launchTest whether people read a change before accepting it, then set targets