Diamond 3 — Toward a Solution
Generating candidates, screening them against what the women said, and the point where the record stops
The team carried one validated pain into this diamond: anxiety when commuting at night, especially in unpredictable or poorly lit environments, already costing time and money to avoid.
Chapters: Ideate Many Solutions and Hypothesize a Good Solution. Guide: Solution Guides.
What is genuine on this page, and what is not
The screening matrix below is the original team’s own work, recovered from course files. Its ideas, its reference solution, its ratings and its decisions are theirs.
Everything around it is reconstructed: the generation session, the requirement provenance, and the test results. The team did diverge, converge and test, but this method did not exist in this form when they worked, and those artifacts are gone. What you are reading is a plausible route to a real destination.
Diverge — Generating Candidates
6-3-5 Brainwriting
Unknown. What could relieve this pain? The team held one validated pain and no solution, and the risk they named was the obvious one: that they would generate three variations of the idea they already liked.
Design. Five people, three ideas each, five minutes a round, six rounds, sheets passing right. The pain statement at the top of every sheet, phrased as a cost rather than a gap: she rearranges her route, her timing and her attention to manage a risk she cannot put down. No discussion during rounds; debrief afterward.
Everyone arrived with four ideas already written down: three they thought might work, and one they knew was terrible. The bad ones went onto the sheets in round one alongside the rest, so they were circulating from the beginning rather than quarantined in a round of their own.
Execution. Thirty minutes. The bad ideas people brought did more work than their share, and they did it by being in circulation rather than by being collected.
Evidence. Roughly ninety distinct concepts. Sorted loosely, they fell into two families: something you carry, and something that tells somebody where you are. A third and much smaller family proposed changing the environment rather than equipping the person, with better lighting and staffed routes, which nobody could act on but which nobody deleted either.
One sheet, reproduced whole, because the count is not the interesting part. Watch what each round does with the round before it.
| Round | What was written |
|---|---|
| 1 | A whistle on a keyring · an app that texts a friend when you press it · (brought bad idea) clothing that shocks whoever grabs you |
| 2 | A whistle that also sends a text · an app that texts only if you fail to check in · a jacket that lights up when you slow down |
| 3 | A bracelet you squeeze · a phone app that cancels the alert when you get home · a pendant that only your contact can see light up |
| 4 | A bracelet that sends without a phone · an app that alerts your contact if you miss your arrival time · a clip-on fob for a bag strap |
| 5 | A wristband that alerts unless you cancel it · a fob that buzzes back to confirm someone got it · a locket with the button behind the stone |
| 6 | A ring with the button under the stone that buzzes to confirm · a keychain fob that does the same · a pendant version for people who do not wear rings |
Round one is first thoughts, and they are obvious apart from the bad idea somebody brought. Round two is the first evidence anyone is reading rather than writing: texts a friend becomes texts a friend if you fail to check in, which is a different product. By round four the phone has quietly dropped out. By round five the confirmation has arrived, and the button has gone under a stone.
Nobody proposed the ring in round one. It is a round-six object, and it did not exist until five rounds of other people’s sheets had happened to it. That is the argument for the method: the ring is not anybody’s idea.
Knowledge update. The pool was large and narrow. Ninety ideas across two families is one idea wearing many hats, and the team recognized it: the count looked healthy and the variety did not. That is what sent them into recombination rather than straight to screening.
Next steps. Recombine before screening, and deliberately cross the two families.
Recombination
Unknown. Brainwriting had arrived at a worn object with a hidden button and a confirmation buzz, and nobody could say why that shape rather than another. Six rounds of building had produced it by feel. The question was whether it held up when taken apart deliberately, and whether there was anything better beside it.
Design. Work the catalog rather than generate afresh, after the session rather than during it. SCAMPER over the strongest candidates, then the SIT templates on the two families in turn.
Execution. Four passes, worked out loud, because the intermediate objects are the part that cannot be summarized. The rule was the closed world: nothing allowed in that was not already in the concept or its surroundings.
| Move | Applied to | The object it produced | What it turned out to be for |
|---|---|---|---|
| Subtraction | an app that texts a friend when you press it | Remove the phone. A thing that texts a friend with no phone in it. | It has to be worn and connected some other way, which is what the room had already groped its way to by round four. The template explains the ring rather than inventing it. |
| Subtraction | a worn button that sends when pressed | Remove the press. Something that sends while you do nothing. | Either it detects, which nobody could build, or it sends unless cancelled. The check-in inverts. |
| Task unification | a ring with a button and an indicator light | The jewelry itself does a second job: the band is the antenna, the stone is the button. | Removes the part that made it look like a device rather than a ring, which is what made it discreet. |
| Multiplication | one alert to one contact | Copy the alert and change the copy: a second, different alert. | A quiet one to a friend and a loud one nobody controls. Rejected, and it is why escalation got written down as something to avoid. |
Evidence. Two subtractions met where brainwriting had already arrived: a small worn object, on the body, that sends without being unlocked. That convergence is the useful part. Six rounds of intuition and two deliberate templates reached the same object by different routes, which is a better reason to trust it than either route alone.
Task unification then did something the session had not: it put the button under the stone, and in doing so removed the last thing that made the object read as a device.
The fourth move produced nothing usable and was still worth running. Deterrence was the team’s own assumption, and this is where they first saw it fail on contact rather than at the $100 test, where it failed again.
Knowledge update. The interesting axis was not what the thing is but whether it is already in your hand when you need it. That distinction survived into testing and turned out to be what separated the two survivors.
Next steps. Screen the recombined candidates against the women’s requirements.
The Bad-Ideas Round
Everyone was asked to arrive with one, and the instruction was the sharp version: not merely useless, but something that would make her situation worse. Five people, five bad ideas, in circulation from round one.
- Electrified clothing. Shocks anyone who grabs the wearer, including the wearer.
- A siren with no off switch. Once it is triggered it runs, whatever she wants.
- A tracker the employer can read. Somebody always knows where she is, and it is not her choosing who.
- A panic button that calls the police. Automatically, and whether or not she wants them to arrive.
Each of those is harmful in a different way: by injuring her, by taking away her control, by handing surveillance to the wrong person, by escalating something she wanted to defuse. That spread is the round working. Four bad ideas that are all bad in the same way would mean the team had found one objection rather than four.
Why that round paid for itself
Shock clothing was never going to survive screening, and it did two things on the way out.
It was the concept the team described to women in the community, and their reaction produced two requirements nobody had held before anything was proposed: not usable against me if an assailant took it, and not dangerous to bystanders if it fired by accident.
Working out why it frightened them produced the ideas that made the surviving concept more discreet and more wearable. The bad idea was the parent of a good one.
Seeding them at the start rather than collecting them in a round of their own is what made that possible. A bad idea written in round four has two rounds left to be built on. The same idea written in round one has five, and it spends them traveling round the table being answered.
What the Catalog Held
After recombination, the candidates worth screening included:
- electrified shock clothing, to send a charge through anyone who grabs the wearer
- non-jewelry accessories that track and send a distress call, hidden in a headband or ear buds
- jewelry that sends a distress call at the press of a button, such as a ring
- a concealed knife carried for defense, on the person rather than in a bag
- noise makers loud enough to scare an assailant away and draw attention
- light-emitting devices intended to stun an assailant or deter an approach
- a keychain that sends an alert and confirms to the wearer that it was received
Converge — Screening
The Market Requirements
Seven, and the provenance is mixed in the way the chapter warns it will be. Some came out of exploration. Two did not exist until a concept was put in front of someone.
| Requirement | Where it came from |
|---|---|
| Stops an assault | exploration; the reason the project exists |
| Discreet, rather than visibly deterrent | exploration; several women preferred to scare an assailant off than to advertise a defense |
| Looks like real jewelry | reaction to an early mock-up |
| Looks and feels feminine | reaction to an early mock-up |
| Works without the phone | exploration, unprompted: the first thing they grab is your phone |
| Confirms the alert was sent and received | assumption, held by the team |
| Not usable as a weapon if taken | reaction to the shock-clothing concept |
The Screening Matrix
Unknown. Which candidates were worth the cost of testing, given what the women had said they needed.
Design. Each candidate rated against Mace, the best thing these women actually had, on each requirement: better, the same, or worse. Unweighted, because every requirement on the list was a gate.
This is the team’s own matrix.
| Reference: Mace | Alert Ring | Taser Wearables | … | Alert Keychain | |
|---|---|---|---|---|---|
| Discrete | = | + | + | … | + |
| Feminine | = | + | – | … | + |
| Confirmed Alerts | = | = | = | … | + |
| … | … | … | … | … | … |
| Non-weaponized | = | + | – | … | + |
| Pluses | 0 | 5 | 2 | … | 5 |
| Equals | N | 2 | 2 | … | 0 |
| Minuses | 0 | 2 | 3 | … | 2 |
| Net Score | 0 | 3 | -1 | … | 3 |
| Decision | reference | improve | combine | … | improve |
Two concepts went forward: the alert ring and the alert keychain. The taser scored minus one and was marked combine rather than dropped, which is the matrix doing what it is for — the concept dies and its one advantage, genuine discreteness, is carried into the survivors.
Knowledge update. Two survivors rather than one, and a requirement list that had just grown by two entries it did not have when screening began. The list was already out of date.
Note what the matrix does not say. A net score of three means better than pepper spray on three more counts than it is worse. It does not mean the ring is the right thing to build, and the team did not treat it that way.
Next steps. Take both survivors to the women who had been talking to them, and find out whether either produced anything beyond approval.
Test — What They Ran
Both survivors went to the women who had been talking to them all along.
Wow Factor
Unknown. Whether either survivor produced any emotional pull, or only polite approval. The team had two concepts that screened well and no idea whether anyone actually wanted one.
Design. Both concepts presented to the same group, in the same session, in randomized order. Rating one to ten on emotional connection, then the four question sets: what appeals, what benefit, what they dislike, what would stop them. Closing with what would make them more likely to buy.
Execution. Run with women already known to the team from the exploration conversations, which is a limitation the team recorded rather than hid: these were people invested in the project and inclined to be kind.
Evidence. The ring drew stronger reactions than the keychain, and the reason was not the technology. A keychain is a thing you carry and might leave in a bag; a ring is already on your hand. The objections clustered on credibility rather than desire — whether something that size could do anything useful, and what happens when the battery dies. Nobody objected to the idea of being tracked, which the team had expected to be the sticking point.
Knowledge update. Already in your hand is the attribute doing the work, and it was not on the requirement list. It had come out of recombination and nobody had written it down as a requirement, which is how a requirement list goes stale between passes.
Next steps. Add it as a requirement and re-screen. Find respondents with no prior relationship to the team.
What that sample can and cannot support
Testing on people who already know you and already care about the project inflates every warm signal and suppresses every objection. It is fine for finding out what the objections are, which is what this round was for. It is not evidence of demand, and the team did not treat it as such.
$100 Test
Unknown. Which features carry the value, and whether the concept was doing one job or several.
Design. Eight candidate features listed, including three the team expected to lose. Each respondent given a hypothetical hundred dollars to allocate. Ranking and spread to be read rather than the totals.
Execution. Run immediately after the wow factor session, with the same limitation.
Evidence. Allocations concentrated on two features: the alert working without unlocking a phone, and confirmation that somebody had received it. Appearance drew money, and less than the team expected. Nothing at all went to the two features that escalated a confrontation — an alarm and a light intended to deter.
Knowledge update. Concentration rather than scatter says the concept is doing one job, which is what you want before building. And the two features that drew nothing were not neutral: they were the ones the team had assumed a safety product needed. Deterrence was the team’s instinct, not the women’s.
Next steps. Build the minimum around those two features. Drop deterrence entirely.
Where the Record Stops
Here. No smoke test, no landing page, no profit analytics.
That is where the original project stopped, and stopping with it is more honest than manufacturing an ending. The team had a concept, evidence that the pain was real, and evidence that two features carried the value. What they never had was a working relationship, and the innovation died on the bench rather than in the market.
Smoke testing is coming, and not as screenshots.
A landing page rendered as images and captions is not a landing page. You cannot see what a visitor sees, and you certainly cannot click. Real smoke-test pages, explorable rather than pictured, are being prepared separately at nilehatch.com.
Until then, the smoke test procedure carries what to build and what to count.