OpenBuilder
Customer Conversations
Plan useful conversations, learn how people work today and use what you find to make a clearer venture decision. Bring a customer group or problem to investigate; no product or previous course is required.
Leave with a customer research portfolio
Work through eight classes with written teaching, exercises and field assignments. Produce source-linked notes, examine contradictory cases and decide what the evidence changes. The course includes a clearly labelled fictional practice path.
Use what you learn
How to run a customer interview
Write down the decision you face and what evidence could change it. Invite someone who recently made a relevant purchase, tried a workaround or walked away. Ask permission to take notes.
What should I ask a potential customer?
Ask about one recent occasion before describing your idea. Follow the sequence from the first sign of a problem to what the person actually did.
Four questions to take to an interview
- Walk me through the last time this happened. What set it off?
- What did you try first? Who else was involved?
- What did that cost you in time or money? What did you do instead?
- What happened in the end? Is there a receipt, message or other record you feel comfortable showing me?
Which parts of an interview count as evidence?
Keep the participant’s words, what you observed and your explanation in separate notes. Record the date and use a participant code so you can trace the account without sharing their identity.
Read three notes from the fictional Gulu repair shop
- Quote from the technician — “I called two suppliers before I could quote. By then the customer had left.”
- Observation — With permission, the interviewer saw two outgoing calls in the phone log that morning.
- Inference to check — Waiting for the part cost the sale. Ask the customer what drove the decision to leave. Price and urgency are also plausible explanations.
How many interviews are enough to change my idea?
Start with a small batch, for example three people who handled the same problem differently. Keep interviewing if a buyer group is missing or conflicting accounts would change your decision. Once the evidence points to a small, reversible test, run it.
Choose whom to interview next
- The first technician remembers losing a customer. Seek a technician whose customer waited and paid despite a delay. Compare the urgency, price and promised collection time.
- If the person using the service and the person paying for it differ, speak with both. Before investing in a full app, test whether customers will actually use or pay for the proposed service.
How do I turn feedback into a product decision?
Group examples by situation and outcome. Pick one change, decide what you will measure and write down which result would make you revise it.
Design a small test for the repair shop
- For comparable urgent jobs, try confirming stock by phone before quoting. Record how many customers accept out of all those quoted, the price and the promised collection time. Compare with similar recent jobs.
- If confirmed availability helps customers commit, keep testing the call-first service. If customers leave after hearing the price even with stock confirmed, investigate pricing before building an ordering app.
Did waiting for a spare part cost the repair shop a sale?
Fictional OpenBuilder example
In this fictional Gulu Repair Link interview, start with a recent job. Ask “Walk me through the last repair where a spare part was missing.” Follow up with “What did you do next?” and “What happened to the job?” Leave the proposed ordering app out of the conversation.
Record what the technician told you: “I called two suppliers before I could quote. By then the customer had left.” With permission, you see two outgoing calls in the phone log that morning. The calls are an observation. The customer leaving is a reported event. Why the customer left is still an assumption.
Keep the contrasting account next to the first. Another technician travelled twice for a part and the customer waited and paid. Both jobs involved a delay, but only one reportedly lost the sale. Ask about urgency, the price quoted and what the customer actually said before treating stock availability as the cause.
For the next urgent repairs, note the promised collection time, when stock was confirmed and whether the customer went ahead. If jobs repeatedly fall through while stock is uncertain, try confirming stock by phone before quoting on comparable jobs. If people leave after hearing the price even when stock is confirmed, investigate price instead. Choose the next test from the difference in outcomes.
How many conversations are enough? For this shop, first include both urgent and routine jobs and seek an account that challenges the pattern. When another interview is unlikely to change the next small test, run it. An expensive commitment such as building the app calls for stronger behavioural evidence before spending.
What you will produce
Customer research portfolio
Choose the right starting point
Stage: Pre-idea → growth. Study at your own pace and allow time for fieldwork. Reading and watching alone do not establish a venture result.
Course outline
Choose a decision worth learning about
Replace a broad customer claim with a focused question connected to a real commitment.
Work to bring back: A dated research decision brief with two learning questions and an explicit contrary signal. Dated source references or an explicit statement that evidence is not yet available. A clear practice or real-work label. A traceable link between the belief and the decision.
Choose the people and situations that matter
Recruit for relevant experience and decision roles rather than a convenient demographic label.
Work to bring back: A participant eligibility card, decision-role map and first-round coverage plan. Qualification reasons connected to the research question. Known versus assumed decision roles. An explicit account of likely recruitment omissions.
Recruit with a clear invitation
Make a relevant request, learn from access problems and keep recruitment assumptions visible.
Work to bring back: An invitation record and recruitment log showing what happened, what changed and whose perspective is still missing. Actual invitation versions and dated approach outcomes. Eligibility reasons for scheduled conversations. A distinction between declined, unanswered and scheduled requests.
Build and rehearse a useful guide
Prepare focused questions that invite concrete experience while leaving room to follow an unexpected account.
Work to bring back: A versioned interview guide with rehearsal feedback and a clear separation between exploration and concept feedback. Guide versions with a date and evidence mode. Specific observer examples rather than a general positive rating. A reason linking each major revision to a learning problem.
Conduct the first field conversations
Listen closely, investigate recent episodes and preserve enough context to understand the account later.
Work to bring back: A first-round interview packet with dated notes and a documented improvement in interview practice. Notes from conversations that actually occurred or clearly labelled practice sessions. Context sufficient to interpret each account. A visible distinction between the participant’s report and the founder’s inference.
Observe the work, then ask about it
Study a real activity and distinguish what happened from the explanation attached to it.
Work to bring back: An observed activity sequence with participant explanation, alternative interpretation and method limits. Date, participant reference, context and method. A sequence of specific observed or reconstructed events. Explicit notes about researcher influence and unseen parts of the process.
Find patterns without losing differences
Build findings that can be traced to notes, challenged by contrary cases and narrowed when necessary.
Work to bring back: A source-linked synthesis table and a justified follow-up plan. References linking major findings to underlying notes. Visible contrary cases and unanswered questions. Counts with a clear denominator and no population claim.
Turn discovery into a decision and a habit
Explain what you learned, choose the next action and continue learning as the venture changes.
Work to bring back: A discovery portfolio, decision memo and continuing learning plan with explicit practice or real-work status. Dated records for the fieldwork claimed. A traceable connection from research to the decision. A reviewed sharing excerpt and actual reviewer feedback where available.
OpenBuilder is an independent course provider. The course credits its source frameworks and separately licensed resources; participation does not imply source-author or university accreditation.