01
Name the moment
Describe the person, their situation and the friction—not just the feature someone requested.
Mobile product field guide
Make room for the next right decision.
Girelumax is a practical reference for teams shaping a mobile app: frame the opportunity, put a prototype in someone’s hand, and learn what deserves attention next.
Problem framingPrototype reviewsResearch moments
Start smallOne question, one scenario, one thing to learn.
Grounded questionsKeep the learning target visible.
Mobile in contextNotice the moment around the screen.
Shared languageBring choices into the open.
A working approach
Move from a signal to a decision your team can explain.
The useful work happens between a promising idea and a clear next step. These prompts help make that work visible.
02
Make it tangible
Sketch the smallest believable path through the moment, then use it to invite specific reactions.
03
Choose deliberately
Turn observations into a decision log: what changed, what stayed uncertain and what comes next.
A better brief
Before screens, define the job people are trying to finish.
A mobile app rarely lives in a blank room. A strong product brief includes the environment, the interruption, the hand holding the device and the consequence of getting stuck.
- Who is trying to make progress, and what is already demanding their attention?
- What does a useful outcome look like from their point of view?
- Which uncertainty would change the next product decision?
Planning studio
Choose the lens that fits the conversation.
Switch between two planning views. Both stay intentionally lightweight so a team can adapt the language to its own context.
Bring the product conversation back to a choice.
Use this view when a team is weighing where to focus. It draws a simple line from context to a working assumption and then to a reviewable moment.
Context
What situation creates the need?
Assumption
What are we choosing to believe for now?
Evidence
What would make the choice more credible?
Prepare a conversation people can genuinely answer.
Use this view when you need to learn about behavior. A clear session gives a participant room to show their own route, rather than rewarding them for agreeing with a proposed solution.
Prompt
Invite a story about a recent moment.
Scenario
Set up a task without supplying the path.
Capture
Record the words, pauses and workarounds.
Three useful lenses
The same idea changes when you examine it from another angle.
Human
What is the person protecting, avoiding or hoping to accomplish in this moment?
System
What other services, people or constraints shape the route through this task?
Interaction
What must be understood, selected or confirmed on a small screen at the right time?
A simple cadence
One small loop can carry a lot of learning.
1
Frame
Write the decision and the uncertainty beside it.
2
Make
Build only enough to make the scenario discussable.
3
Meet
Watch someone work through the moment in their own words.
4
Reflect
Compare notes and agree on the decision that follows.
Prototype with purpose
A prototype is a question in a form another person can respond to.
It does not need to settle every state or reveal a polished identity. It needs to create a believable situation where the team can see whether an interaction makes sense.
Open the review checklistA useful reframe
“The goal is not to prove that a screen works. It is to understand what a person expects to happen next.”
Keep the focus on the person’s path, not a defense of the draft.
Show a real situation
Use a prompt that places the task in a familiar moment and avoids naming the answer.
Invite a narrated path
Ask what someone notices and expects before asking whether they like an interface.
Review checklist
Set up the next review in a few deliberate moves.
Filter by the work in front of you, then check off the prompts that matter for this session. Your selections stay in this browser while you explore.
Session ready?
0 selectedWrite it in plain language before the discussion begins.
Give people context without directing their next action.
Remove unrelated paths that could distract from the question.
Separate what was seen or heard from the team’s interpretation.
End with a shared next step, a remaining question or both.
Field notes
Thought starters for practical mobile work.
Three reminders to bring into a working session—not a fixed method, just a place to begin.
Make ambiguity visible
When an assumption is written down, people can challenge it, improve it or decide it is not the one that matters.
Listen for workarounds
What someone does around a product can be as revealing as what they do inside it.
Leave a trace of why
A small decision note helps future collaborators understand the context instead of reliving the debate.
Questions, considered
Frequently asked questions.
A few common questions from teams that are making space for product learning alongside delivery work.
An early brief should describe the person, their context, the progress they are trying to make and the uncertainty the team needs to reduce. It can also state a working assumption and the decision it may influence. Treat it as a conversation aid rather than a final specification, so it remains easy to revise after new observations emerge.
Make the portion of the experience that supports the question believable enough to discuss, and let the rest stay intentionally simple. If you want to learn whether someone notices a next step, show the surrounding context and that step. If visual treatment is not part of the question, avoid letting polished decoration pull attention away from the interaction you want to understand.
Start from a real situation and invite someone to show how they would approach it in their own words. Watch for the expectation behind each tap, as well as hesitations and workarounds. Afterward, distinguish direct observations from interpretations. This keeps the discussion connected to evidence while leaving room for thoughtful design judgment about the next move.
Give every review a named decision and capture the outcome in a short, shared note. Include what the team observed, what it now believes, what is still uncertain and which choice follows. That record creates continuity across design, engineering and product conversations, while making it easier for a new collaborator to understand the reasoning behind the current direction.
Start a local draft
Share the question your team is working through.
This form creates a private draft in your browser only. For a general note, write to [email protected].
No submission is sent from this site.