Studio culture & creative process / DIJION
A creative prototype session: exploring one question with constraints
A workshop plan connecting time and material constraints to a learning question, including comparisons and discarded prototypes.
A short prototype session does not need to produce a finished product. For an illustrative one-tap game, the aim may be to examine understandable timing rather than finalize the character’s appearance. Constraints can help focus work, but an arbitrary deadline without a learning question may create pressure to produce quickly without learning anything useful.
What should the session distinguish?
Write the uncertainty between two control ideas, explanations or task sequences. Also define what the prototype cannot show. A paper flow cannot measure real touch responsiveness, though it may support discussion of understandable choices. Let the question guide the medium instead of making the team’s familiar tool the only deciding factor.
Choose constraints for a reason
Scroll the table horizontally to see all columns.
| Constraint | Question examined | Risk of overinterpretation |
|---|---|---|
| One input action | Is the control concept understandable? | Claiming the whole game is enjoyable |
| Placeholder visuals | Can the flow be followed? | Judging final visual quality |
| Fixture data | Is the hierarchy sufficient? | Inferring production performance |
Compare alternatives against the same task
Comparisons become misleading if each idea receives a different, easier task. Keep initial conditions, explanations and observation questions comparable. An earlier attempt may teach the later one, so record the order. Separate the preference a participant states from the actions observed instead of assuming one automatically explains the other.
Preserve why an idea was set aside
Setting a prototype aside does not make the session a failure. Leave a short record of question, observation, interpretation and next step. If the evidence is inconclusive, say so rather than declaring the most attractive idea a winner. Mark file locations and shortcuts that should not migrate into product code without further work.
A session closing checklist
- Compare the original question with the observations.
- List conditions the prototype did not examine.
- Record why ideas were kept or set aside.
- Distinguish product implementation from another experiment as the next step.
This is a workshop template rather than a report of completed studio research. Its value lies in describing uncertainty more clearly before producing more screens.