Frugal Innovation in Practice
Global Innovation Management - TUHH Institute for Technology & Innovation Management · part of my Technology Management MBA · study notes for revision.
The last chapter defined what frugal innovation is. This one is about how you actually do it. It operationalises the M3 frugal segment we met before - the buyers who want appropriate technology, only the core functionalities, genuinely good quality, but who are very price-sensitive. This chapter turns that target into a working method: a six-step process, developed at TUHH’s Center for Frugal Innovation, for taking a product from “is this even worth doing?” all the way to a market launch that a frugal customer will actually pay for.
1 · The six-step Frugal Innovation Process
Section titled “1 · The six-step Frugal Innovation Process”The Center for Frugal Innovation lays the work out as a pipeline. Each step answers one question and hands the next step a clear input, so the whole thing reads top-to-bottom like a funnel: Should we? → What exactly? → What’s the concept? → Build it → Prove it → Launch it.
The rest of the chapter walks each step in turn - and picks out the three places where frugal work is genuinely different from ordinary product development: getting at sticky customer needs (step 2), designing to a cost target rather than a feature list (steps 3-4), and hunting down cost drivers systematically (step 6).
2 · Step 1 - Analysis of relevance
Section titled “2 · Step 1 - Analysis of relevance”Before spending a euro on development, you decide whether the frugal game is even yours to play. This is a detailed analysis of three things and an evaluation of two:
- Market development - where is demand heading?
- (New) competitors - who is here, and who is arriving?
- Market position - where do we actually stand today?
- Chances - what could the frugal segment win us?
- Risks - what happens if we ignore it, or get it wrong?
The lecture frames this as an honest self-check. It is worth keeping the questions almost verbatim, because they are the ones a management team should be able to answer out loud before committing:
- Which markets are strategically important to us, and how important are the emerging markets specifically - and which ones?
- How important is the frugal M3 segment for us, today and in the future - and does that differ between industrialised and emerging markets?
- Have customer needs and preferences changed - have we actually witnessed a shift in demand?
- Are there established or new competitors - from industrialised or emerging markets - who are strong in M3, or fast-growing there?
- And the scary one: are any of those competitors upgrading their portfolio to move up into the M2 and M1 segments - that is, using a frugal foothold to attack your premium business from below?
3 · Step 2 - Need analysis and development goals
Section titled “3 · Step 2 - Need analysis and development goals”If step 1 says “yes,” step 2 goes and finds out what the customer actually needs - and this is where frugal innovation gets its own distinct discipline. Four moves:
-
Stand up an international, interdisciplinary project team. Frugal needs live in the target market, so the team has to reach into it - not sit entirely in the home-country R&D lab. Different functions and different countries on the same team.
-
Do comprehensive market segmentation and define the target customer group precisely - a long list narrowed to a criteria-based short list, finalised with people in-country, not from a spreadsheet at head office.
-
Run explorative and quantitative market research - a mix of qualitative digging ((n)ethnography, workshops, on-site observation) and quantitative validation (questionnaires, test runs). Explore first to find the real needs; then measure to size them.
-
Convert needs into specifications using structured tools - the Kano model to sort features by how much satisfaction they buy, and the House of Quality (QFD) to translate customer wants into engineering targets.
In practice the lecture shows this running as a small, disciplined workflow: a customer long-list is drafted by the local team, narrowed to a criteria-based short-list finalised in-country, and a workshop and questionnaire design is drafted at home, then test-run in both places - Germany and the target market - before the real research begins. The pattern is always the same: draft centrally, validate locally.
3.1 The “sticky information” problem
Section titled “3.1 The “sticky information” problem”Here is the deep reason frugal research can’t be done from a desk in Germany. Eric von Hippel observed that some knowledge is “sticky” - costly and difficult to move from where it lives to where it’s needed. Customer need-knowledge is exactly this kind of sticky information: it’s tied up in habits, contexts and workarounds the customer themselves can barely articulate. You cannot email it to yourself. So the Center’s rule of thumb is that frugal need research has to happen:
Two India examples from the lecture make it concrete - and show how needs a distant team would never guess surface the moment you watch people at home:
| What on-site observation revealed | The need a distant team would miss |
|---|---|
| Fridge storage habits. Traditional storage containers and cooking routines mean families plan their fridge space very differently - bulky vessels, batch-cooked food, specific layouts | A “standard” shelf and drawer layout designed for Western groceries simply doesn’t fit how the fridge is actually loaded |
| Storing insulin in a hot climate. India is among the countries with the highest and fastest-growing diabetic populations - and insulin must be kept cool | The fridge isn’t just for food. Reliable, stable cold storage becomes a health requirement, changing what “core functionality” even means |
The point generalises: the fridge’s real job description was written in Indian kitchens, not in a European product-planning meeting. Only being there, with the right local partners, watching the actual use, exposes it.
3.2 Netnography, defined
Section titled “3.2 Netnography, defined”One of the explorative tools deserves its own definition, because the name is odd:
3.3 Turning needs into specs - Kano and House of Quality
Section titled “3.3 Turning needs into specs - Kano and House of Quality”Raw needs aren’t buildable; specifications are. Two tools bridge the gap:
| Tool | What it does | Why it matters for frugal |
|---|---|---|
| Kano model | Sorts features into basic (expected - their absence angers), performance (more is linearly better), and delight (unexpected, disproportionately pleasing) | Tells you what you can safely strip out (never a basic), where “more” is wasted spend, and where a cheap delighter earns loyalty |
| House of Quality (QFD) | Quality Function Deployment - a matrix that maps customer requirements onto engineering characteristics, with target values | Forces every engineering target back to a real customer need, so cost-cutting removes effort without removing benefit |
4 · Step 3 - Concept development and product planning
Section titled “4 · Step 3 - Concept development and product planning”Now you shape the actual concept, and the frugal discipline sharpens to a single instruction: do less, better, for less. Based on the market research, the concept work concentrates on:
All three serve the productive contradiction at the heart of frugal work: reduce effort while increasing benefit. Ordinary cost-cutting sacrifices benefit; ordinary premium design piles on cost. Frugal design refuses both and treats “cheaper and more useful” as a problem to be solved, not a trade-off to be accepted.
The methods here are the ones you’d expect for creative problem-solving: structured ideation and design thinking - the human-centred loop of empathise → define → ideate → prototype → test. Design thinking fits frugal work naturally because it starts from the user’s real context (exactly the sticky need-knowledge from step 2) rather than from the engineering that’s easy to reach for. An ideation-and-design-thinking workshop is a good way to force the “core only” and “reduce effort, increase benefit” constraints onto the table early, while the concept is still cheap to change.
5 · Steps 4 & 5 - Development, prototyping and testing
Section titled “5 · Steps 4 & 5 - Development, prototyping and testing”Concept in hand, you build it - but against three yardsticks at once, and to a cost target rather than a feature wish-list:
- Technical specifications - the buildable spec from QFD
- Cost requirements - target costing - the allowed cost is set first, from the market price the customer will bear, and the design must hit it
- The competition - benchmarked against what rivals already offer in M3
- Internal standards - do our own norms fit a frugal build, or fight it?
- Processes - are they geared for low-cost, higher-volume output?
- Methods - are our design-for-cost / design-for-manufacture practices good enough?
Target costing is the quiet star here. In conventional development you design the product, then add up what it costs. In target costing you invert it: market price minus desired margin equals allowable cost, and that number becomes a hard design constraint from day one. It is what stops “just one more feature” from creeping the price back out of the M3 segment.
Then step 5 - prototyping and testing - makes the concept physical and puts it in front of real users to check that the benefit survived the cost-cutting and the cost survived the benefit. Design thinking’s build-and-test loop lives here too: prototype, learn, refine.
6 · Step 6 - Production and market introduction
Section titled “6 · Step 6 - Production and market introduction”The final surprise of frugal innovation is that a frugal product needs a frugal business model. You cannot bolt a low-cost, price-sensitive product onto a premium company’s machinery and expect the numbers to work. The frugal business model requires adjustments across four levers:
| Lever | The frugal adjustment |
|---|---|
| Procurement strategy | Source strategically for cost - often in the target region - instead of defaulting to home-country suppliers |
| Location of production | Produce where it makes cost and market sense, close to demand and low-cost inputs |
| Marketing / branding | Position honestly for the segment - quality and trust at an accessible price, not a stripped-down apology |
| Distribution strategy | Reach price-sensitive customers efficiently - rethink channels, direct-vs-indirect sales, e-commerce |
Even the channel question loops back to the customer: the lecture pairs this step with a fresh study of customer experiences and preferences - for example, whether buyers in the segment actually prefer direct or indirect sales. Distribution is a cost lever, but it is also a need to be researched, not assumed.
6.1 Hunting cost drivers with an Ishikawa (fishbone) diagram
Section titled “6.1 Hunting cost drivers with an Ishikawa (fishbone) diagram”To find where all that cost is really being created, the Center uses an Ishikawa diagram - also called a fishbone or cause-and-effect diagram. You write the problem in the fish’s head (“costs are too high”), then draw “bones” for each category of the value chain, and hang the specific contributing causes off each bone. The power of it is that it forces you to look across the whole value chain at once, so you stop blaming the obvious culprit and see that cost is created in many places - some far from where it shows up on the invoice.
Here’s the diagram from the lecture, regrouped by category (the effect at the head, causes grouped by bone):
Effect: “Costs are too high” - driven by causes across four areas of the value chain:
- Purchasing & suppliers
- Over-specification of parts (paying for performance the frugal customer never needs)
- Low cooperation with suppliers
- Missing strategic purchasing on the Asian market
- Less focus on sourcing and designing-in low-cost components
- Supply chain & logistics
- A single central hub in Germany (long, expensive routes to the target market)
- Expensive packaging
- Production & process
- Too many manual steps versus low automation - and no design for automation
- High-mix / low-volume production (little economy of scale)
- Optimised development for production missing; design-for-manufacture and design-for-test improvable
- Specific, time-consuming testing and complex equipment needed
- Sales & marketing
- Overhead-heavy sales, low use of e-commerce, no direct-to-customer channel
- Overhead-heavy marketing (print material, fairs)
- A modular development approach missing (so nothing is reused across variants)
7 · The frugal mindset
Section titled “7 · The frugal mindset”The chapter closes on the thing that ties all six steps together. Frugal innovation is not a one-off cost-cutting exercise you run at the end; it is a way of thinking that has to be developed proactively, all along the process - present in step 1’s honest self-check, step 2’s on-site listening, step 3’s “core only,” step 4’s cost target, and step 6’s rebuilt business model.
Revision summary
Section titled “Revision summary”That completes the module. Back to the course overview - from the basics of innovation, out to the global stage, and down to doing more with less.