Turn an ITE Course Project into a Customer Problem Interview

Tom — Singapore Digital Business & Systems Consultant

Tom

Digital Business & Systems Consultant · Singapore

7 min read Article date First published
Turn an ITE Course Project into a Customer Problem Interview

To turn an ITE course project into customer research, treat the project as a question, not a product. Find five people who might have the problem it addresses, ask neutral questions about what happened the last time, show your demo only at the end, and record what you heard, including anything that contradicts your idea. You are learning, not selling. If the problem turns out not to be real, that is still a useful result, and the project still counts for class.

Key takeaways

  • A course brief tests your skills; a market problem exists whether or not you build anything.
  • Ask about the last time something happened, not whether someone would use your idea. Show the demo last.
  • Ask before taking notes, write roles instead of names, and check your school's rules before reusing coursework outside class.
  • Summarise with counts and contradictions, then continue, change the question or park the idea. No sales pitch.

Separate the project brief from a market problem

Your lecturer's brief assesses skills, such as a working login or a clear report. It does not have to prove that anyone outside class needs the result. A market problem is something people already struggle with and work around, whether or not you build anything.

The project brief asksThe market question asks
Does the demo meet the marking criteria?Does anyone struggle with this today?
Which features did you build?What do people already do instead?
Will the lecturer accept it?How often does it happen, and what does it cost in effort?

A project can score well and still solve a problem nobody has. Before interviewing, write it as one testable sentence: "I think [type of person] struggles with [task] because [reason]." The interview tests that sentence, not your code.

Before you start: permission, notes and school rules

  • Who to ask. Five people who might have the problem, such as a family business and nearby shop owners. Never your employer's customers or anyone found through workplace records.
  • Ask before taking notes. Say it is a school project, you are not selling anything, and they can skip a question or stop.
  • Write roles, not names. "Owner, framing shop" is enough. No phone numbers, photos, screenshots or customer details.
  • School rules. Check your school's rules and your lecturer before reusing coursework outside class, including showing a demo.
  • Under 18 or on a Student's Pass? A learning interview involves no selling or payment. If anyone offers to pay, first read the cautions in my guide to side hustles for ITE students.

My advice, not a rule: if you are under 18, tell a parent or guardian who you are meeting and where, and interview at a business during opening hours or in a public place.

Explaining the purpose first is good practice, not a legal checklist. It echoes Personal Data Protection Commission guidance that consent requires telling people what their information is for.

Prepare five neutral questions

A leading question signals the answer you want: "Wouldn't an app make this easier?" usually gets a polite yes. A neutral question asks about something that already happened, so each answer is a story you can compare.

The five-question interview sheet

Copy this onto one page and fill the blank from your project sentence.

  1. 1"Tell me about the last time [situation] happened." A real, recent example, not an opinion about the future.
  2. 2"What did you do next, step by step?" The current workaround: what your idea would have to beat.
  3. 3"Which part took the most time, or went wrong?" The cost: minutes, rework, mistakes, waiting.
  4. 4"How often does that happen in a normal week?" One bad day is a story; every day is a pattern.
  5. 5"This is a demo I built for a class project. Where would it fit what you just described, and where would it not?" Show the demo only now, so it cannot shape the first four answers.

Close with "Is there anything I should have asked?", thank them and stop. Keep it to about 15 minutes at a quiet time.

Rewrite leading questions

Avoid (leading)Ask instead (neutral)
Would you use an app for this?What did you do the last time this happened?
Don't you find this frustrating?Which part takes the most time?
How much would you pay for my app?Leave price out; you are learning, not selling

Summarise evidence without forcing a sale

Resist two temptations: counting every polite comment as support, and asking the friendliest person to buy. A pitch makes people polite instead of honest. Write a one-page summary with counts, not impressions.

Evidence summary template

FieldWhat to writeExample (fictional)
Project sentenceYour guess, unchangedFraming shops lose time answering whether orders are ready
Who you spoke toRoles and number, no namesFour owners, one counter staff member
Problem described unpromptedHow many told a story about it in answers 1 to 41 of 5
Current workaround and costWhat they do now, and the effortCustomers call or message; replies take seconds
Demo reactionWhere it fits and where it does notMight suit a busy shop; small shops prefer messaging
Contradicting evidenceAnything against your sentenceFour of five said status questions are quick
DecisionContinue, change the question or parkChange the question: uncollected orders

My rule of thumb, not a proven threshold: if fewer than three of five describe the problem unprompted, it is probably not a market problem yet. Change the question or park it.

A fictional example: when the answers contradict the idea

(fictional example) Irfan is on an IT-related Higher Nitec course. His class project lets a shop's customer type an order number and see whether the job is ready. His aunt runs a picture-framing shop, so his sentence is: small framing shops lose time answering "is it ready yet?"

After checking with his lecturer, he spends three weekends on five interviews: his aunt, three shop owners and one counter staff member whose owner agrees. He asks before taking notes and writes no names. Two shops decline, and one interview is cut short.

The answers contradict his idea. Four of five say status questions take seconds by phone or message; only his aunt calls it a problem, and family answers lean kind. But four mention something he never asked about: customers who do not collect finished frames, which means storage space and repeated reminders.

The upside: an honest summary and a sharper question. The effort and uncertainty: three weekends, no sale, no app, and no proof that uncollected orders cost enough to solve. Next: three interviews on that question alone.

When a repeated problem might need a tool

Most interview rounds end with a better question, not a product. If the same costly problem keeps coming up across different people, try a spreadsheet or a form first, as my problem notebook guide suggests.

An internal workflow, such as jobs passing through WhatsApp and spreadsheets, is what operations digitalisation addresses. Something people log in to, such as a booking tool or client portal, is web app development, which I scope and quote individually once the problem is proven.

Your next step

Write your project sentence, copy the five questions and book one interview outside your family. A finished summary, with names left out, also makes strong material for a student portfolio that shows how you solve business problems.

Sources (checked 31 October 2026)

Frequently Asked Questions

Can I interview a family business?

Yes, it is often the easiest place to start. Family tends to be kind, so count it as one interview and include people you do not know well.

What if the answers contradict my idea?

That is a useful result. Record the contradiction, keep the coursework for class, and change your question or park the idea.

How many interviews do I need?

Five is a reasonable start for a learning exercise, not statistical proof. Look for the same story repeating across different people.

Should I try to sell my project at the end of the interview?

No. The interview is for learning. If someone asks to pay, pause and check the cautions for your age, pass and school rules first.

Can I show my coursework to people outside school?

Check your school's rules and your lecturer before reusing coursework outside class, and ask before your first interview.

Finished your interviews, and the same problem keeps coming up? Send me your evidence summary, with no names, and I'll give you an honest view of whether it might ever need a web app or whether a simple form will do. It is a conversation, with no commitment, and your studies come first.

No obligation. No sales pitch. Just an honest conversation.

お問い合わせ