This site uses cookie tracking technologies. Learn more in our Cookie Policy.
The moment your IA gets decided (before you build anything)
There’s a quiet moment in every IB Design Technology class where the room splits in two. One group starts sketching something impressive: a “smart” device, an ambitious mechanism, a product that looks like it belongs in a Kickstarter video. The other group does something less exciting but far more powerful: they write down a real person’s problem and how they’ll prove they solved it.
That second choice is where high scores usually begin in IB Design Technology. Not because examiners love “simple” projects, but because a good IA topic creates evidence. Evidence is what the rubric can reward.
Sticky-note IA chaos
If you’re trying to choose an IA topic while also preparing for exams, your best strategy is to pick a topic that is clear, testable, and realistic. Then you can keep revision moving using the IB Design Technology hub and tools like Questionbank, Study Notes, Flashcards, AI Chat, and Mock Exams.
The most common trap in IB Design Technology is starting with a product you feel like making.
“Desk organiser.” “Smart bottle.” “Phone stand but cooler.”
Those are objects, not design opportunities.
A stronger start sounds like this:
“My user is a left-handed student who smears ink when writing quickly. Current solutions don’t fit their desk setup. I can test smudge reduction and comfort.”
“My user has limited grip strength. Existing jar openers require twisting force they can’t apply. I can measure torque needed before and after.”
Notice what’s happening: the topic is already writing your evaluation section for you. That’s the hidden advantage in IB Design Technology: when the problem is well framed, your research, requirements, testing, and reflection become easier to justify.
Choose a user you can reach (and who will tell the truth)
A “good user” in IB Design Technology is specific and available. Ideally, you can meet them multiple times, ask follow-up questions, and run real testing sessions.
Good user options:
A family member with a repetitive daily task
A teacher with a classroom routine problem
A sports teammate with equipment frustration
A specific group with shared constraints (one club, one class, one workplace)
Avoid vague users like “students” or “people who like fitness.” Vague users lead to vague requirements, and vague requirements lead to weak testing.
Comfort ratings with a consistent scale plus short interviews
A topic that forces you into “It feels better” without structure is risky in IB Design Technology. You can still include user feelings, but anchor them to measurable design requirements.
A simple project gives you room to do the real work: iteration, testing, and honest evaluation. A complex project often steals that time.
Think of IB Design Technology like this: the prototype is not the point. The decision-making is.
Rubric monster chooses the simple path
If your topic requires advanced electronics or coding you don’t understand, your documentation becomes a story of guesswork. If your materials are hard to source, your timeline collapses. A “manageable” IA is usually the one that lets you show repeatable evidence.
Use existing products as benchmarks, not templates
You’re allowed to use existing products in IB Design Technology. In fact, it can strengthen your justification because you can show what already exists and why it fails your user.
A strong approach:
Identify a specific weakness in the current solution
Link it to user data (quotes, observations, measurements)
Improve function or performance, not just appearance
This also makes testing easier, because you can compare your solution against the benchmark product.
A final way to choose: pick the topic that generates proof
A good IB Design Technology IA topic doesn’t need to be flashy. It needs to be defendable. Choose a real user, define one clear problem, and build a solution you can test honestly.
