What discovery is for at Kwark
Discovery answers one question before anything is designed: is there a real person with a real problem here, and what is the smallest thing that helps them? Kwark’s principle 2 is “a problem before a feature”: copying a competitor is never a reason, and a feature that cannot name the person and the situation in one sentence does not start.
Kwark has no research team and, today, no panel of users to interview on demand. That makes honesty about evidence part of the method, not a footnote.
Who Kwark is for
These are the people every decision is tested against. They come from the founder’s brief and the mission, not from a survey.
| Person | Their situation |
|---|---|
| The part-time filmmaker | A student or working professional who wants to make films but cannot do it full time. Writes after a ten-hour shift. |
| The first-time writer | Unsure, sometimes afraid. Needs the way to begin to be obvious and one step away. Students from 13 years old are included. |
| The indie production | A short timeline and a short shoot. Accuracy and time saved matter more than features. |
| The crew on the day | A 1st or 2nd AD, a DOP, an actor, on a phone with bad signal, holding a printed call sheet. |
| The writer in India and beyond | Writes in Tamil, Hindi or another Indian script; works under rules that differ by country. |
The state Kwark protects for all of them is calm: nothing competes with the page, nothing counts, grades or nags, every state says the work is safe.
The discovery steps
- Name the need in one sentence. Who, in what situation, blocked by what. The principle’s own example: “indie shoots are short, so every scene shows its runtime and the timeline shows talk against action.”
- Say what happens if Kwark does nothing. If the answer is “nothing much”, stop.
- Find the real job. What is the person trying to get done, in their words? A second AD’s job is not “manage call sheets”; it is “make sure 23 people arrive at the right place at 06:30 with the right pages”.
- Name the paper. If the film industry already has a paper artefact for this job (a marked-up script, a stripboard, a call sheet), that is the shape of the answer. See Specs and handoff.
- List the assumptions that could be wrong across value (do they want it?), usability (can they use it?), feasibility (can we build it on the free tier?) and viability (should Kwark do it at all, given its rules?).
- Pick the riskiest one and the smallest test. A mock-up shown to the founder, a built screen in the preview, a role simulation, a single real shoot. Write what result would change the plan.
- Decide, and record why. Two or three options with costs; recommend one; the founder decides anything expensive to reverse.
Evidence: what counts and how to say it
- Must say where every claim about people comes from: the founder’s words, a real shoot, a support message, a code audit, a simulation.
- Never invent research, metrics, users or quotes. No “users told us”, no “studies show”, no made-up percentages.
- Never present an agent’s role simulation as user research. It is a rehearsal that finds where a design breaks, labelled “simulated”. The review ladder uses them on purpose (a 1st AD, an actor, a line producer, a writer in Tamil), and their findings are design defects to check, not evidence of what people want.
- Always write the honest limit beside a claim: “checked at 375 wide with touch emulation; not on a real phone”, “read from code; nobody ran it on a device”.
- Always put the founder’s own words in quotes when they are the source.
The audit as discovery
The 17 October 2026 audit (docs/ux/audit/SUMMARY.md) is a good model of honest discovery from code. It opens: “All findings are from reading code; nobody ran the app on a device. Verify each before fixing.” It found real problems a writer would meet (the idle curtain that would blank a pitch after 60 seconds, a UTC “today” that gave India yesterday before 05:30, Cmd+S making a snapshot nobody asked for) and ranked them by what they cost the person, not by how hard they were to fix.
Asking few questions, then deciding
Discovery with the founder is not an interview. He answers in feelings and outcomes; he tires of questions with obvious answers.
- Must ask two or three questions at most, and only those that change what gets built.
- Always state your call for anything with an obvious default, in one line, and record it.
- Always show something (a mock-up, a screen) and let the reaction do the work.
A good question: “Should the sample film open in the visitor’s library, or only in a pop-up?” A question that should have been a decision: “Should the button say Start or Begin?”
When a real person is available
When the founder has a producer meeting, a shoot, or a writer friend, discovery uses them well:
- Ask about the last time, not the future: “Tell me about the last call sheet you sent.” Not “Would you use a call sheet tool?”
- Ask what they tried and what they did not love about it.
- Never pitch during the conversation. Write down their words exactly.
- Watch them use the real screen, on their own phone if possible. Real-device and screen-reader checks need a person; agents cannot do them from here.
Rules
- Must name the person, the situation and the problem in one sentence before naming a feature.
- Must say what happens to the person if Kwark does nothing.
- Never treat “a competitor has it” as the need.
- Never fabricate research, quotes or numbers, or present simulations as research.
- Always test the riskiest assumption first, with the smallest test that could change the plan.
- Always run the need through Kwark’s rules: no judgement, nothing social, structure optional, free tier.
“Need: a second AD reprints the call sheet at 2 a.m. and nobody can say which version the crew holds. Source: Wave 3 plan and the call sheet review.”
“Need: 78% of ADs want version control.” (No such survey exists.)
AI readiness test
Task. Decide whether Kwark should add a cast availability calendar.
Give the agent. This page, Product skills, the mission, Decision 0043 (calendar for artists).
Constraint. No invented evidence; label any simulation.
A reliable answer
- States the need in one sentence with a named person and situation
- Lists value, usability, feasibility and viability assumptions
- Picks one smallest test and the result that would change the plan
- Labels role simulations as simulated
- Checks reads and writes against the free tier