Howard Chan
Howard Chan
Wrote this guide · international school, Tokyo
IB 45 / 45 (predicted) Incoming Cambridge HSPS Tokyo · UK·US·HK

The IB Design Technology (DT) Internal Assessment (IA) is often perceived as a beast, but it's genuinely one of the most rewarding IAs if you approach it strategically. As someone who scored a 7 in DT and achieved a 45 overall, I can tell you that the IA is a significant chunk of your final grade (40% for SL, 20% for HL) and a prime opportunity to demonstrate your understanding beyond rote memorization. This guide isn't about generic advice; it's about the concrete steps, timelines, and thought processes that helped me succeed, drawing from my experience at an international school in Tokyo.

Unlike some other IAs, the DT IA is a comprehensive design project, from initial problem identification to final evaluation. It demands not just technical skill but also strong project management and critical thinking. My own IA focused on designing a portable, modular desk solution for students in small living spaces – a problem I genuinely observed among my peers. The key to a high score isn't necessarily inventing something revolutionary, but rather executing each stage of the design process with rigor, reflection, and clear evidence.

Understanding the Criteria: Your Blueprint for Success

Before you even think about a project idea, internalize the IB DT IA criteria. These are your marking rubrics, and every single sentence in them is a directive. The criteria are A: Analysis of a design opportunity, B: Conceptualisation and planning, C: Developing the solution, D: Testing and evaluating, and E: Applied design. I printed them out and highlighted keywords, constantly referring back to them during each stage of my IA. Your supervisor will also use these, so knowing them inside out allows you to 'design' your IA to meet their expectations.

For instance, Criterion A demands a 'detailed analysis of the design opportunity, including the needs and wants of the client/target user and the synthesis of research.' This isn't just about stating a problem; it's about demonstrating empathy, conducting primary research (interviews, surveys), and using secondary research (existing products, materials) to justify your chosen direction. My initial mistake was thinking a simple problem statement was enough; I quickly learned the depth required.

Choosing Your Design Opportunity: Relevance and Scope

This is arguably the most critical early decision. Your design opportunity needs to be genuinely interesting to you, allowing for sufficient depth of exploration without being overly ambitious. Think about problems you or your community face. For me, the cramped living spaces in Tokyo and the struggle students had with dedicated study areas sparked my idea. Avoid overly broad topics like 'sustainable housing' – narrow it down to a specific, manageable problem, e.g., 'a modular storage system for small student dorm rooms using recycled plastics.'

Consider the resources available to you. Do you have access to specific workshops, materials, or experts? My school had a well-equipped workshop, which influenced my decision to design a physical product. If your school lacks certain facilities, you might lean towards a digital solution, a system design, or a product that relies more on readily available materials. Always discuss your initial ideas with your supervisor to ensure they are viable and offer enough scope for all criteria.

Criterion A: Analysis – The Foundation of Your IA

This is where you set the stage. My approach involved a multi-pronged research strategy. I conducted a survey of 30 students to understand their desk usage patterns and pain points, followed by in-depth interviews with 5 key users. This primary research provided concrete data for my user profile and design specifications. Alongside this, I researched existing portable desks, material properties (e.g., plywood vs. MDF for strength-to-weight ratio), and relevant ergonomic standards.

Crucially, synthesize your research into a concise 'design brief' or 'design specifications.' These are measurable, testable statements that your final product must meet. Instead of 'it should be portable,' write 'the desk must be easily collapsible by one person in under 30 seconds and weigh less than 5kg.' Each specification should be directly traceable back to your research. This shows the examiner you've thought critically about the problem and its constraints.

Criterion B: Conceptualisation and Planning – Iteration is Key

Don't just present one idea. This criterion rewards divergent thinking and iterative development. I started with brainstorming sessions, sketching dozens of rough concepts. Then, I selected 3-4 promising ideas and developed them further with annotated sketches, 3D CAD models (I used Fusion 360), and even simple cardboard prototypes. For each concept, I performed a 'decision matrix' or 'Pugh chart' to objectively evaluate them against my design specifications, justifying why I chose one over the others.

Planning involves detailed technical drawings (orthographic, isometric, exploded views) with dimensions and material specifications. I also created a Gantt chart for my project timeline, detailing tasks, deadlines, and resources. This demonstrates project management skills. Remember, the examiner wants to see your thought process, not just the final product. Show your mistakes, your learning, and how you refined your ideas based on feedback or further research.

Criterion C: Developing the Solution – The Build Phase

This is where your chosen concept comes to life. Document every step of your fabrication process with clear photographs and concise descriptions. If you're building a physical prototype, show the tools you used, the techniques applied (e.g., 'dovetail joint for increased strength,' 'sanding with P240 grit for smooth finish'), and any challenges encountered. My desk design involved complex joinery, and I documented the trial-and-error of cutting precise angles on the table saw.

For digital solutions, this means showing the development of your code, UI/UX wireframes, or system architecture. Explain your design choices and justify them with reference to your specifications and research. If you make modifications during the build, explain *why* you made them – perhaps a material wasn't available, or a joint proved too difficult to execute. This shows adaptability and problem-solving, which are highly valued.

Criterion D: Testing and Evaluating – Objective Assessment

This is not just about saying 'it works.' You must objectively test your prototype against your *measurable* design specifications. For my desk, this involved timing how long it took to assemble/disassemble, measuring its weight, and conducting user trials where participants rated its stability and comfort using a Likert scale. I also performed load-bearing tests to ensure it met safety standards. Present your data clearly, using tables, graphs, and qualitative feedback.

The evaluation section requires you to reflect on your project's success and limitations. Did it meet all specifications? If not, why? What improvements could be made? This isn't about blaming external factors; it's about critically assessing your own design and process. Propose concrete modifications for future iterations, demonstrating a continuous improvement mindset. This shows a deep understanding of the design cycle.

Criterion E: Applied Design – Your Holistic Reflection

This criterion is often misunderstood. It's not a summary of your IA; it's a holistic reflection on how well you've applied the principles of design and technology throughout your project. Think about the broader implications of your design. How does it address social, ethical, environmental, or economic issues? My desk IA touched on material selection (sustainability), ergonomics (user well-being), and affordability (economic viability).

Discuss your learning journey. What new skills did you acquire? What challenges did you overcome? How has your understanding of the design process evolved? This is your opportunity to demonstrate higher-order thinking and a mature understanding of DT as a discipline. Connect your experiences back to core DT concepts and theories learned in class.

Timeline and Managing Your Supervisor

Start early! I began brainstorming in May of Year 12, had my design opportunity finalized by September, and aimed to complete my prototype by January of Year 13. This gave me ample time for testing, evaluation, and refining my report before the school's internal deadline in March. Procrastination on the IA is a common pitfall. Break down the project into manageable chunks and set mini-deadlines for yourself.

Your supervisor is your greatest resource. Don't just show up to meetings saying 'I'm stuck.' Come prepared with specific questions, drafts, or problems you've encountered. Ask for feedback on specific criteria. For example, 'Does my research in Criterion A adequately justify my design specifications?' or 'Are my testing methods robust enough for Criterion D?' Proactive engagement with your supervisor can make a significant difference to your final score.

Frequently asked questions

The IB recommends 50 hours for SL and 60 hours for HL. Realistically, expect to spend more, especially if you're aiming for a top score. I probably spent closer to 80-100 hours on mine, spread out over several months. Consistent effort is more effective than last-minute cramming.
Absolutely! The IB DT IA allows for a wide range of solutions, including digital products (apps, websites), system designs (e.g., a waste management system for a school), or even service designs. The key is to ensure it allows you to address all criteria comprehensively, especially the 'development' and 'testing' aspects.
There isn't a strict page limit, but quality over quantity is crucial. Aim for conciseness and clarity. For HL, a typical report might be 30-50 pages, including appendices (sketches, photos, CAD files). Focus on presenting evidence effectively and directly addressing each criterion. Avoid excessive waffle.
For CAD, popular choices include Fusion 360 (free for students), SolidWorks, or SketchUp. Choose one you're comfortable with and can produce professional-looking drawings. For the report, Microsoft Word or Google Docs are standard. Ensure you use consistent formatting, clear headings, and high-quality images.
Yes, it is absolutely okay! The IA is about the *design process*, not just the final product. Examiners understand that prototypes are often limited by time, resources, and skill. What matters is that you demonstrate critical reflection on its limitations, identify areas for improvement, and justify your design choices throughout. A 'perfect' prototype with a poor report will score worse than a flawed prototype with an excellent, reflective report.
The takeaway

The IB Design Technology IA is a demanding but highly rewarding project that tests your entire design thinking process. By deeply understanding the criteria, choosing a relevant and manageable design opportunity, conducting thorough research, documenting your iterative development, and critically evaluating your solution, you can achieve a top score. Remember to engage proactively with your supervisor and manage your time effectively, focusing on demonstrating your learning journey and problem-solving skills rather than just presenting a flawless final product.