A product development studio. Technical and human realities, mapped before design begins.

Scroll
—Architecture before execution. —Clarity before the sketchbook opens. —Constraints are not limitations. They are the specification. —Structure before form. Always. —Every decision has a documented reason. —Tradeoffs made consciously, not by default. —Products fail not from lack of effort — from lack of structure. —Thinking guide rails, not formulas. —Architecture before execution. —Clarity before the sketchbook opens. —Constraints are not limitations. They are the specification. —Structure before form. Always. —Every decision has a documented reason. —Tradeoffs made consciously, not by default. —Products fail not from lack of effort — from lack of structure. —Thinking guide rails, not formulas.
§01
What we are
Product development studio
How we work
Technical realities first. Briefs before sketches.
Status
● Accepting briefs
Entry point
Signal Sprint™
Product development studio · Harare, Zimbabwe

The brief determines the product.

A product development studio. Technical and human realities, mapped before design begins.

Find the fault lines → Book a free intake call

We interrogate the formula, we don't follow it

  • 15-domain product interrogation
  • 14-day Signal Sprint™
  • 7-component Clarity Report
  • Manufacturing-network backed
§02
The cost
Three structural failures. All avoidable. All expensive.

Most product problems are decided before design begins.

01

Manufacturing surfaces late

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.

02

Domains pull against each other

Cost, regulation, tolerance, and use impose competing demands. Resolved consciously, they define the product. Left unresolved, they collide in production.

03

False certainty

Teams commit to a form before the assumptions under it are tested. The render looks resolved. The structure underneath was never checked.

§03
Authority
The person behind the method. The work is the proof.

Why founders bring us in before design begins.

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.

The studio is young. The method is not. It is the documented structure behind how products are actually scoped, tested, and defended before money moves. Every framework on this site was built from real engagements — not theory that sounded right.

See the work →
§04
Fig. 01
The five fault lines the formula never asks you to find. Every failed product contains at least one of these.
Engineering Orange
marks structural risk

The places where
product development
gets expensive.

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.

FAULT 01

The wrong brief

The specification that governs everything contains assumptions nobody tested.

FAULT 02

Form before reality

The render was produced before manufacturing constraints, cost structure, and material specifications were mapped.

FAULT 03

The unasked question

One question would have changed the direction. Nobody asked it because the process didn't require it.

FAULT 04

Unmapped constraints

Regulatory, supply chain, tolerance, assembly — each a potential stopper that was completely avoidable.

FAULT 05

The formula ran

The process was followed correctly. The product launched and failed. The formula doesn't check whether the brief is right.

Signal Sprint™

Finds these fault lines before they find you — at the cheapest possible moment.

Read what it produces →
§05
Section
How we work
Framework
The Product Method™
Phases
Define · Architect · Execute

The Product
Method™

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.

01

Define

Interrogate the brief. Map constraints, assumptions, and risks across all domains before any design begins.

Signal Sprint™
02

Architect

Translate the defended brief into specification architecture — tolerances, material logic, manufacturing strategy.

03

Execute

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 →
§06
Work
Four engagements. Each one traced from assumption to clarity.
Format
Problem · Constraint · Resolution · Outcome

From assumptions
to clarity.

Four engagements. Each one interrogated from first principles.

01 / 04
Dual-arm monitor mount — structural detail Fig. 01
01

Dual-Arm Monitor Mount

Hardware B2B2B
Problem

A resolved form that could not be manufactured. Design decisions were made without interrogating tooling constraints or production realities.

Constraint

Die-cast aluminium tolerances, dual-axis cable routing, VESA compliance across 15 kg load range.

Resolution

Full constraint hierarchy rebuilt from tooling up. Specification architecture preceded form — not the other way.

Outcome

Complete decision foundation documented. Every structural choice traceable to a defended constraint.

Read case study →
Aeris PureMist humidifier — bedroom context Fig. 02
02

Aeris PureMist HM-S01

Consumer End-to-End
Problem

The humidifier market is designed for Northern Hemisphere climates. Southern Africa's dry savannah sits below comfortable humidity most of the year — and no product addresses it.

Constraint

Ultrasonic atomisation at consumer price point. Water-safe enclosure. Single-hand operation under 180 g. Must read as furniture, not medical device.

Resolution

47-participant research, 7-brand competitive audit, three CAD iterations. Constraint hierarchy locked before any form was drawn. CMF across three colorways. Full brand identity and companion app UI.

Outcome

Complete product, brand, and interface system — designed from climate data, not trend boards. Manufacturing path mapped across three supplier tiers.

Read case study →
TOW campus bikes — students riding on university grounds Fig. 03
03

TOW Campus Bike

Urban Mobility Systems Design
Problem

University campuses spread across grounds that take 20 minutes to cross on foot. No existing bike-share system is designed for the constraints of campus — short hops, high turnover, zero maintenance budget.

Constraint

Single-speed mechanics. Belt drive — no chain, no oil, no maintenance downtime. Tool-free saddle adjustment. Basket large enough for a laptop bag. 50-unit fleet managed by one team.

Resolution

Frame geometry optimised for short urban hops, not speed. Modular front basket, integrated lighting, recessed branding. Docking station handles unlock, tracking, and overnight charging from a single kiosk.

Outcome

Complete product and system specification — bike, docking infrastructure, and fleet operations designed as one integrated architecture.

Read case study →
Fig. 04
04

Oryx Mobile Lodge System

Modular Systems Architecture
Problem

Safari tourism has a structural problem. Guests stay in permanent lodges far from the park and commute into the reserve. The experience of being within nature is never achieved.

Constraint

Flatbed transport width limits. Off-grid energy autonomy. Seasonal climate range from −2°C to 42°C. Zero permanent footprint — the park must remain undisturbed.

Resolution

Self-contained modular units deployed directly within game parks. Split-level plan, floor-to-ceiling glazing, skylight module. Module dimensions derived from logistics constraints — not aesthetics.

Outcome

Full system specification — single unit to temporary village. Deployable, reconfigurable, relocatable. No foundations, no permanent infrastructure.

Read case study →
View all work →
Qualification
Read these. If two or more describe your current situation — Signal Sprint™ was built for this moment.

Anti-Førmula is built for you if —

01

You're building a physical product and the technical complexity is starting to show.

02

You've invested in product development before and want the next stage built on solid ground.

03

Your brief doesn't feel complete — and you're not sure what's missing.

04

You're about to spend real money and want to know the foundation is solid first.

Not for you if you're building a digital product, SaaS, or app. Anti-Førmula is built for physical product development only.
§07
What it is
The complete product architecture framework. Applied across the full development lifecycle.
Structure
Define → Architect → Execute
Relationship
Signal Sprint™ is the thinking guide rail for the Define stage

The Product
Method™

The complete framework for architecting a product from structural ambiguity to defended execution. Three stages. Outside-in and inside-out simultaneously.

Phase 01

Define

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.

Thinking guide rail → Signal Sprint™
Phase 02

Architect

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.

Thinking guide rail → Constraint Hierarchy
Phase 03

Execute

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.

Thinking guide rail → Decision Log

Not a formula. A structured sequence of thinking that gives every decision a foundation it can be held to.

Read the full method →
§08
The position
The founding argument. Every sentence was arrived at by looking at the industry honestly.
See also
Full founding statement →

Why we believe the brief determines the product

01. Physical products have a specification that goes deeper than most briefs.
02. Manufacturing constraints. Regulatory requirements. Material science. Cost structure. Supply chain realities. Each one determines whether the product can actually exist as designed.
03. When these aren't mapped before design begins, they surface later. At tooling. At first assembly. At the moment a manufacturer asks for a specification that doesn't exist.
04. By then, addressing them costs ten times what it would have at the start. A single unmapped constraint can cost $15,000–$40,000 to correct. Some cost the entire project.
05. Products fail not because of a lack of effort. They fail because of a lack of structure — decisions made too late, questions never asked, assumptions never tested.
06. We work in the stage before that. Before the brief is accepted. Before the sketchbook opens. Before a line is drawn.
07. The technical layer isn't the obstacle. It's the specification.
Start
First step
A 30-min intake call — no charge, no commitment
Response
Within 24 hours

Ready to start?

Architecture before execution.

The brief determines the product. The Signal Sprint™ determines the brief.

Start a brief → See Signal Sprint™