Unit 6: Innovation Project, Re-Design and Product Presentation - Subjective Questions

Design iteration is the repeated process of designing, testing, evaluating, and improving a product or solution. It helps designers gradually move from an initial concept to a more effective final product.

Importance of design iteration:

• Reveals usability, technical, and functional problems at an early stage.
• Allows designers to incorporate user feedback into later versions.
• Reduces the risk and cost of making major changes after production.
• Encourages experimentation and learning from failure.
• Improves the product's usability, desirability, feasibility, and sustainability.

A product is rarely perfect in its first version. Iteration makes the design more responsive to real user needs and changing conditions.

The main principles of effective design iteration are:

• User-centred development: Improvements should be based on genuine user needs and observed behaviour.
• Rapid experimentation: Designers should create and test prototypes quickly instead of spending excessive time perfecting one idea.
• Evidence-based decisions: Changes should be supported by testing results, data, and feedback rather than personal assumptions.
• Incremental improvement: Each version should address specific weaknesses while preserving successful features.
• Openness to failure: Failed prototypes should be treated as sources of learning.
• Cross-functional collaboration: Designers, engineers, marketers, and users should contribute to the improvement process.
• Clear evaluation criteria: Every iteration should be judged against defined goals such as usability, cost, safety, or performance.

Product re-design is the systematic improvement of an existing product to solve identified problems or meet changing user and market requirements.

Typical re-design process:

• Study the existing product and identify its strengths and weaknesses.
• Collect user feedback and analyse competing products.
• Define the specific problems that require improvement.
• Generate alternative design concepts.
• Develop and test prototypes.
• Select the most suitable concept using technical, economic, and user-based criteria.
• Implement, evaluate, and refine the revised product.

Re-design usually retains some existing features, brand identity, infrastructure, or manufacturing methods. A completely new product, in contrast, begins with a new problem or opportunity and may require a new target market, technology, and production system.

User feedback can be collected through several qualitative and quantitative methods:

• Interviews and focus-group discussions.
• Surveys and questionnaires.
• Direct observation of users performing tasks.
• Usability tests with prototypes.
• Reviews, complaints, and support requests.
• Usage analytics and performance data.
• A\slash B testing of alternative design versions.

Feedback analysis involves:

• Organising responses into themes or categories.
• Separating facts from personal opinions and assumptions.
• Identifying repeated problems and high-impact complaints.
• Giving greater importance to issues that affect safety, accessibility, or essential tasks.
• Comparing feedback with the original design objectives.
• Converting findings into clear design requirements.

The analysis should result in prioritised actions rather than an unstructured list of comments.

Qualitative feedback describes users' experiences, feelings, explanations, and difficulties in words. It helps answer questions such as why a user is confused or what users value about a product.

Examples:

• An interview in which users explain that a control is difficult to understand.
• An observation showing that users hesitate before completing a task.
• A comment stating that the product feels uncomfortable to hold.

Quantitative feedback is numerical and can be measured or compared statistically. It helps answer questions such as how many users experienced a problem or how long a task takes.

Examples:

• The percentage of users who complete a task successfully.
• The average time required to complete a process.
• The number of errors made during testing.
• A satisfaction score collected through a survey.

Both types are valuable: qualitative data explains the reasons behind problems, while quantitative data indicates their scale and frequency.

A design team should prioritise feedback systematically instead of responding to every comment equally.

Recommended approach:

• Group similar comments into common problem areas.
• Measure the frequency of each issue.
• Evaluate the severity of the problem for users.
• Consider the effect on safety, accessibility, and essential functionality.
• Identify the number and importance of users affected.
• Estimate the technical effort, cost, and time required for a solution.
• Check whether the proposed change supports the project's objectives.
• Address critical and high-impact issues before minor aesthetic preferences.

A useful prioritisation matrix can compare impact with effort. High-impact, low-effort improvements are usually implemented first, while high-impact, high-effort changes require strategic planning.

Design refactoring is the process of restructuring or simplifying an existing design without changing its essential purpose. The term is commonly associated with software, but the same idea applies to physical products, services, interfaces, and systems.

Role in product re-design:

• Removes unnecessary features, steps, or components.
• Simplifies the user experience.
• Improves consistency and maintainability.
• Reduces manufacturing complexity or technical debt.
• Improves performance, reliability, and accessibility.
• Preserves valuable functionality while correcting weaknesses.

For example, a mobile application may be refactored by reorganising navigation and removing duplicate screens while retaining its main services. Refactoring is different from adding features because its primary goal is to improve the structure and quality of the existing design.

The transformation of feedback into a re-designed product can follow these stages:

1. Collect feedback: Gather observations, comments, performance results, and usage data.
2. Organise findings: Group feedback into themes such as usability, appearance, reliability, cost, and accessibility.
3. Identify root causes: Determine why the problem occurs instead of addressing only its visible symptom.
4. Define design requirements: Convert user problems into measurable statements, such as reducing task time or improving grip comfort.
5. Generate solutions: Develop multiple concepts that respond to the requirements.
6. Build prototypes: Represent the most promising ideas at an appropriate level of detail.
7. Test and compare: Evaluate the prototypes with representative users and technical criteria.
8. Implement and monitor: Develop the selected solution and continue gathering evidence after launch.

This process ensures that re-design decisions remain connected to real user needs.

Strategic pivoting is a significant change in a product's direction, target user, value proposition, technology, or business model while retaining useful learning and resources from the original project.

A team should consider pivoting when:

• Repeated testing shows that the product does not solve an important user problem.
• The intended users are unwilling or unable to adopt the product.
• Technical limitations make the original concept impractical.
• Production costs are too high for the expected value.
• Market conditions or competitor offerings have changed substantially.
• A different user group shows stronger demand.
• Evidence suggests that another application of the technology is more valuable.

Pivoting should be based on strong evidence. It is not the same as making a minor design adjustment, because it changes the strategic direction of the project.

Incremental improvement involves making small, controlled changes to an existing product. It preserves the main concept and usually focuses on improving usability, performance, reliability, appearance, or cost.

Strategic pivoting involves a major change in direction. It may alter the target market, user problem, product purpose, technology, or revenue model.

Key differences:

• Incremental improvement has a low to moderate level of change; pivoting has a high level of change.
• Incremental improvement is suitable when the core concept is validated; pivoting is suitable when fundamental assumptions are disproved.
• Incremental improvement generally requires fewer resources; pivoting may require new research, skills, and partnerships.
• Incremental improvement reduces known weaknesses; pivoting responds to a major opportunity or failure.

Both approaches support continuous improvement, but the appropriate choice depends on evidence, risk, available resources, and project objectives.

Continuous improvement is the ongoing effort to make a product, service, or process more effective, efficient, reliable, and valuable over time.

It can be incorporated through the following cycle:

• Set measurable objectives for quality, usability, cost, and performance.
• Develop or modify the product based on current knowledge.
• Test the product with users and technical evaluators.
• Measure results against the objectives.
• Analyse failures, complaints, and unexpected outcomes.
• Implement corrective and preventive actions.
• Repeat the process after each significant release or change.

Continuous improvement requires documentation, regular review, ownership of improvement tasks, and a culture in which evidence and learning are valued. It continues after the initial product launch and helps the product remain relevant as users and environments change.

An effective product presentation should communicate the product clearly, credibly, and persuasively.

Essential elements include:

• A clear statement of the user problem or opportunity.
• Identification of the target users and their needs.
• A concise explanation of the proposed solution.
• Demonstration of the product's key features and benefits.
• Evidence from prototypes, testing, user feedback, or market research.
• Explanation of technical feasibility and implementation requirements.
• Information about value, cost, sustainability, or competitive advantage.
• A logical structure with a clear beginning, middle, and conclusion.
• Visuals that support the message rather than distract from it.
• A specific final request, recommendation, or call to action.

The presentation should focus on the value created for users and stakeholders rather than describing every design activity in equal detail.

Design communication should be adapted to the knowledge, priorities, and decisions of each audience.

• Users: Need to understand the product's usefulness, ease of use, safety, and relevance to their daily problems.
• Technical experts: Need detailed information about specifications, architecture, materials, constraints, performance, testing, and reliability.
• Managers: Focus on strategic fit, resources, risks, schedule, operational impact, and expected outcomes.
• Investors: Need evidence of market demand, scalability, competitive advantage, commercial potential, and return on investment.

The core product message should remain consistent, but the level of detail and supporting evidence should change. Effective communication avoids both unexplained technical jargon and vague promotional claims.

A high-impact product presentation is focused, evidence-based, visually clear, and relevant to its audience.

Important characteristics:

• Begins with a significant user problem or compelling opportunity.
• Uses a simple and memorable value proposition.
• Shows the product through a prototype, demonstration, scenario, or visual model.
• Explains benefits rather than listing features alone.
• Uses credible evidence from testing, research, and user feedback.
• Presents information in a logical sequence.
• Maintains an appropriate pace and avoids unnecessary detail.
• Anticipates likely questions and addresses risks honestly.
• Uses readable visuals, consistent terminology, and uncluttered slides.
• Ends with a clear conclusion and requested decision.

Impact comes from connecting the problem, solution, evidence, and value into one coherent story.

The NABC model is a framework for presenting an innovation through four connected elements:

• Need: What important problem, unmet need, or opportunity exists? The presenter should identify who experiences it and why it matters.
• Approach: What product, process, or design solution addresses the need? This section explains the main concept and how it works.
• Benefits per costs: What measurable value does the approach provide, and what resources or costs are required? Benefits may include improved performance, time savings, safety, revenue, or environmental value.
• Competition: What alternatives already exist, and why is the proposed solution better, different, or more suitable?

A presentation based on NABC begins with the need, introduces the approach, proves that its benefits justify its costs, and positions it against competing solutions. This structure keeps the presentation focused on value and evidence.

An elevator pitch should communicate the essential value of a product in a short and memorable form. A suitable structure is:

1. Opening problem: State the important problem or unmet need.
2. Target user: Identify who experiences the problem.
3. Solution: Introduce the product and explain how it addresses the need.
4. Unique value: State the main benefit and what makes the product different.
5. Evidence: Mention a prototype result, user validation, technical achievement, or market indication.
6. Call to action: Request a meeting, pilot, investment, approval, or other specific next step.

A strong pitch uses plain language, avoids unnecessary technical detail, and focuses on outcomes. It should be concise enough to deliver within a few minutes while remaining specific and credible.

A feature is a characteristic, component, or capability of a product. A benefit is the useful result or value that a user receives from that feature.

Example:

• Feature: The device has an automatic power-saving mode.
• Benefit: The user spends less on energy and can operate the device for a longer period.

The distinction matters because users and stakeholders usually make decisions based on outcomes rather than technical characteristics alone. Product communication should:

• Explain what the feature does.
• Connect it to a specific user need.
• Describe the resulting practical or measurable value.
• Support important claims with evidence.

Features are necessary for explaining the product, but benefits make the product relevant and persuasive.

Prototypes and demonstrations provide tangible evidence that a design concept can work and create value.

Their roles include:

• Making an abstract idea easier to understand.
• Showing the product's appearance, operation, and user interaction.
• Demonstrating important features and workflows.
• Supporting claims about usability, performance, and feasibility.
• Revealing the progress made through design iterations.
• Helping the audience visualise the intended final product.

A good demonstration should be planned around a realistic user scenario and a specific presentation objective. The presenter should prepare a backup such as a video, simulation, photographs, or test results in case the live prototype fails. Limitations should be stated honestly so that the prototype is not mistaken for a fully developed product.

A technical design case study examines a design problem, the decisions made, and the evidence supporting the final solution.

Main stages:

• Define the problem, context, constraints, and success criteria.
• Research users, existing solutions, technologies, materials, and standards.
• Identify design requirements and prioritise them.
• Generate and compare alternative concepts.
• Select a concept using criteria such as performance, cost, safety, sustainability, and usability.
• Develop prototypes or technical models.
• Conduct tests and record measurable results.
• Analyse failures, feedback, and trade-offs.
• Iterate or re-design the solution.
• Present the final design, evidence, limitations, and recommendations.

A strong case study explains not only what was designed, but also why particular decisions were made and how the results were validated.

Trade-offs occur when improving one design objective affects another. For example, increasing durability may increase weight or cost.

A team should present trade-offs by:

• Clearly identifying the competing objectives.
• Explaining the alternatives that were considered.
• Providing evidence from tests, calculations, research, or stakeholder feedback.
• Showing why the selected option best fits the project priorities.
• Distinguishing confirmed results from assumptions.
• Stating limitations such as a small test group, incomplete prototype, untested conditions, or unresolved production issues.
• Explaining the risks and proposing actions for future improvement.

Honest discussion of limitations increases credibility. It shows that the team understands the design responsibly and can make informed decisions about further development.