An interesting idea is only a starting point. Before investing heavily in a solution, a team needs to understand the problem, consider alternatives and learn which assumptions deserve testing. Ideation provides a structured way to explore possibilities instead of choosing the first suggestion.
This practical guide from GREEZA Academy & Consultancy, LLC uses a fictional service example. Use the exercises to practice turning observations into ideas and small experiments.
What problem are you trying to solve?
Describe who experiences the problem, what they are trying to achieve and where the difficulty occurs. Separate observations from assumptions. “Customers abandon the booking form after reaching the date-selection step” is more useful than “We need a new app.”
Gather a few relevant observations or conversations before proposing fixes. Ask what users expected, what confused them and how they currently work around the problem. Avoid treating one person's experience as representative of everyone.
How can you frame an ideation question?
Turn the problem into an open question with enough focus to guide the discussion. For the booking example, try: “How might we help a first-time customer choose an available appointment without contacting support?”
This leaves room for several approaches. A clearer calendar, a simpler explanation or a different sequence of questions might each deserve consideration. Starting with a predetermined product would narrow the options too soon.
How can a team generate more than one idea?
Give participants a short period to write ideas individually before discussing them. This creates space for contributions that might otherwise be lost in a fast conversation. Ask each person to explain the problem their idea addresses.
Group related ideas and explore combinations. Keep a record of alternatives rather than discarding them simply because they are unfamiliar. At this stage, the aim is to create options that can be examined.
How should you compare ideas?
Agree on a small set of criteria before voting. For example: usefulness to the intended user, effort required for an initial test, accessibility and the uncertainty involved. Distinguish an attractive presentation from evidence that an idea solves the problem.
Select a manageable idea for a first experiment. Record why it was chosen and what would cause the team to change direction.
What makes an idea testable?
State the assumption and the observation you need. In the booking example, the assumption might be that a simpler calendar helps users identify an available slot. A rough screen sketch could be enough for an initial task-based conversation.
Ask participants to attempt the task without coaching them through the design. Note where they hesitate, what they misunderstand and what they expect next. A small exercise offers learning; it does not prove that the solution will work for the whole market.
What should happen after the test?
Summarize what you observed, which assumptions remain uncertain and what to change next. Decide whether to revise the idea, explore another option or gather more information. Keep the problem statement visible so the team does not lose sight of the original need.
How can you develop your ideation skills?
The Design Thinking Ideation Tools Course listed by GREEZA Academy & Consultancy, LLC introduces ideation methods for developing startup solutions. Review its current details here:
https://greezaacademycourses.learnworlds.com/course/design-thinking-ideation-tools-course-1
Before enrolling, request the syllabus, practice activities, assessment and completion-document details. Contact info@greezaacademy.com for course information.