Prototyping with Lars Laumeyer

In this video, you will learn why prototypes are more than just functional models: they are experiments with a clear hypothesis. Lars Laumeyer shows how you can save time, money and stress with small, targeted prototypes – and focus your development on the essentials.

Learn how to use prototypes to clarify specific requirements, gather genuine user feedback and even carry out design or weight tests – without a fully developed product. Lars Laumeyer shows you how to gain valuable insights and avoid typical pitfalls with small measures.

In this video, Lars Laumeyer shows how you can identify weaknesses early on and avoid costly mistakes with realistic performance tests, objective measurements and well-thought-out test planning – a must for anyone who wants to bring products to market.

Lars Laumeyer provides practical tips on how to quickly create better prototypes with clear goals, realistic expectations, agile planning and a good understanding of your target group – and how to elegantly avoid typical pitfalls.

In this video, Lars Laumeyer shows how you can use frontloading and parallel concept development to set the course right from the start of product development – for lower costs, better products and shorter development times. Includes a lean startup approach and tips on the right prototyping strategy.

In this video, you will learn how AI, CAD and simulation tools are already supporting prototyping today – from quick design mock-ups and 3D models to virtual crash tests. Lars Laumeyer explains in practical terms what you should pay attention to and when it is really worth using these tools.

Perfectionism or blind activism? Both can cost valuable time during prototyping. In this video, Lars Laumeyer shows you how to find a healthy balance between thinking and doing, how to use creative methods sensibly, and how to accelerate development processes with hackathons.

In this video, Lars Laumeyer explains in practical terms how parametric design, reusability, standard components and modular construction make development smarter and more flexible. With clear tips for more structure and less frustration in everyday prototyping.

In this video, Lars Laumeyer demonstrates which manufacturing processes have proven themselves in prototyping – from 3D printing and laser cutting to clever conversions using standard components. You will also learn what to pay particular attention to in terms of safety, product liability and the ‘make or buy’ decision.

In the last video, Lars Laumeyer summarises the most important findings: from the customer perspective to modular concepts to realistic test scenarios. Perfect for anyone looking for a comprehensive overview and wanting to know how to develop innovative products with a systematic approach and focus.

1) Define goal & scope

• • Specify the prototype’s purpose (e.g., demonstrate concept, verify a function, test user flow, collect feedback).
  • Formulate concrete questions/hypotheses (what do you want to learn or falsify?).
  • Limit scope: what’s in this iteration, what’s explicitly out?
  • Set success criteria (how will you know the prototype served its purpose?).

2) Clarify target users & context of use

• • Identify relevant user group(s) and select primary use cases.
  • Describe context of use (location, situation, environment, devices, constraints).
  • Derive key requirements/goals (task sequence, information needs, response times).

3) Choose prototype type & fidelity

• • Select the appropriate type (paper/sketch, mockup/wireframe, click-through/interactive, functional model/hardware).
  • Decide on fidelity (low vs. high): as low as possible, as high as needed.
  • Prioritize assumptions: what must be realistic vs. what can be simplified?

4) Plan methods, materials, and tools

• • Choose methods (e.g., storyboard, task flow, wireframe, click prototype, physical functional model).
  • Gather materials/components (paper, cardboard, 3D print, electronics module, off-the-shelf parts).
  • Select tools/software (e.g., drawing/mockup tool, CAD, build/soldering equipment, test devices).
  • Create a rough timeline (build phase, test window, analysis, revision).

5) Sketch information architecture & flows

• • Capture core functions and user flows (simple sketches or task flows).
  • Define critical interactions (inputs, states, system responses).
  • Note edge cases (errors, exceptions, interruptions).

6) Build the prototype (first iteration—“as early and as simple as possible”)

• • Produce the first working artefact (paper/mockup/click-through/functional rig).
  • Build only what is necessary for the test; exclude everything else.
  • Version clearly (date, changes) and keep brief build notes.

7) Prepare test design

• • Define test goals and measurement points (e.g., task success, time on task, errors).
  • Create a test script/guide (intro, tasks, observation points, debrief).
  • Plan recruitment (who tests, how many, criteria) and set up the test environment.
  • Prepare consent/privacy info if required.

8) Run sessions & collect data

• • Set up realistic test situations (quiet setting, working demo paths, backup materials).
  • Observe rather than lead; only nudge participants when truly blocked.
  • Capture data systematically (observations, quotes, timings, errors, drop-offs, notes).
  • Write a brief post-session log (key problems, aha moments).

9) Analyze & derive actions

• • Evaluate results against hypotheses/success criteria (what was confirmed or falsified?).
  • Cluster and prioritize issues (severity, frequency, impact).
  • Derive concrete improvements (what to change, remove, add).
  • Decide whether the next iteration keeps or changes type/fidelity.

10) Iterate & verify

• • Plan the second iteration (smallest meaningful scope, clear objectives).
  • Implement changes and re-test (same criteria, new sample or comparison).
  • Check progress against goals (visible convergence to required outcomes?).
  • Repeat until core risks are sufficiently reduced.

11) Handover & next steps

• • Create a short documentation (goal, hypotheses, method, versions, results, decisions).
  • Record open issues, risks, and assumptions (to-do list for MVP/development).
  • Define the next maturity step (e.g., more functional model, deeper usability test, tech demo).
  • If relevant: prepare follow-ups (pitch demo, stakeholder review, investor one-pager).