A product development studio. Technical and human realities, mapped before design begins.
A product development studio. Technical and human realities, mapped before design begins.
We interrogate the formula, we don't follow it
A constraint unmapped at brief stage surfaces at tooling — at ten times the cost. A single one runs $15,000–$40,000. Some end the project.
Cost, regulation, tolerance, and use impose competing demands. Resolved consciously, they define the product. Left unresolved, they collide in production.
Teams commit to a form before the assumptions under it are tested. The render looks resolved. The structure underneath was never checked.
Anti-Førmula is led by Tanaka Sande, an industrial designer practising from Harare. Every framework in this studio was built by deconstructing product decisions from first principles — not by following industry trends or best-practice templates. His work covers the full development chain: constraint mapping, specification architecture, manufacturing coordination with factories across China's production network. Real tooling decisions, real tolerance negotiations, real capital at risk.
These are structural realities. Not edge cases — the standard territory of physical product development. Knowable, mappable, and addressable before design begins. The cost of addressing them rises steeply with time.
The specification that governs everything contains assumptions nobody tested.
The render was produced before manufacturing constraints, cost structure, and material specifications were mapped.
One question would have changed the direction. Nobody asked it because the process didn't require it.
Regulatory, supply chain, tolerance, assembly — each a potential stopper that was completely avoidable.
The process was followed correctly. The product launched and failed. The formula doesn't check whether the brief is right.
Finds these fault lines before they find you — at the cheapest possible moment.
Three phases. Each one earns the right to enter the next. No phase is skipped, no deliverable is assumed — because the most expensive product failures start with the decisions no one questioned.
Interrogate the brief. Map constraints, assumptions, and risks across all domains before any design begins.
Translate the defended brief into specification architecture — tolerances, material logic, manufacturing strategy.
Coordinate production across the supply chain. Every decision traced back to the architecture that justified it.
Most studios start at Execute. We start at Define — because that is where products actually fail.
Read the full method →Selected engagements. All structural decisions documented.
Fig. 01 — Case Study / Hardware
A resolved form that could not be built. This case study documents what happens when execution precedes architecture — and why the structure failed.
Fig. 02 — Case Study / Consumer
Personal care device. Constraint hierarchy established before any form was drawn. The structure determined the form — not the other way.
Fig. 03 — Case Study / Systems
Modular lodge system. Product architecture defined the system before any component design began. Outside-in, inside-out simultaneously.
The complete framework for architecting a product from structural ambiguity to defended execution. Three stages. Outside-in and inside-out simultaneously.
Understand before designing. Map the operating context, constraints, regulatory environment, manufacturing reality. Surface every assumption. The Define stage produces the structural brief — the only brief worth executing against.
Build the structural system — not the form, the decisions that make form possible. Component architecture, material logic, tolerance strategy, cost structure. Every decision documented, defended, traceable.
Execute from a verified foundation. Form follows structure — not trend, not preference. Every downstream decision governed by the structural constitution produced in the previous two stages.
Not a formula. A structured sequence of thinking that gives every decision a foundation it can be held to.
Read the full method →Ready to start?
The brief determines the product. The Signal Sprint™ determines the brief.