AI Blocks › Build a product people want
Product weak point redesign
Describe what keeps breaking. Get the part causing most trouble and ways to design it out.
Product weak point redesign is a free AI skill for the job "Build a product people want". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · Made by AI Blocks
What it does
When something keeps breaking, the usual move is to patch the weak part again. A part that causes most of the faults is often a part the design needs for no good reason. Patching it costs you every month, for as long as you keep it. This skill lists the parts and where faults, delays and costs come from, then picks the worst one from the numbers, not from a hunch. It asks why that part has to exist and looks for a design that gets the same result without it. Then it states what the new design costs, checks that the rest of the system still works, and names what to test first.
You give it
- The product, process or system, and what keeps going wrong
- Any records of faults, costs, returns or delays, by part or step (optional)
- What the thing must achieve, and any limits on budget, time or rules (optional)
- A buyer brief (optional)
You get
- A table of parts with their share of faults and costs
- The one part chosen as the main trouble, with the evidence
- Two or three ways to design it out, with the trade-off in one line each
- A system check and the first thing to test
Use it when
- Returns, complaints or repairs keep tracing back to the same area.
- A process has one step that always stalls or needs a person to rescue it.
- You are about to fix the same part for the third time.
How to use it
- Start a chat with the skill. Open it if you added it to your AI, or copy it and paste it in.
- Describe the thing and what keeps going wrong. Paste any fault, return or cost records as they are.
- Say what the thing must still do, so the options do not drop the main result.
- Read the chosen part and its evidence first. Argue with it if the numbers look wrong.
- Run the first test it names before you commit to a redesign.