How to identify opportunities for innovation

How to identify opportunities for innovation: stop asking for ideas. Ideas are cheap. Constraints are expensive. An opportunity is a job that is stuck often enough that a better means would be paid for — in money or in hours.

Three places it hides

Waits: the mill, the inbox, the signature. Rework: scrap, double entry, “send it again.” Hero jobs: only one person can close the month, set up the cell, or talk to the machine.

• If it happens daily, you can measure a test in two weeks.
• If it happens once a year, you have a drama, not a product.
• If only one person understands it, the opportunity might be documenting — not AI.

Customers already built a prototype

The ugly spreadsheet is a requirements document. The taped-up fixture is a patent drawing in cardboard. Do not replace it with a platform until you can say what the hack was doing that the official process was not.

How to tell if this is a real job

“How to identify opportunities for innovation” only matters if someone already does the work and it hurts. Write the job in one line. Write who does it on a Tuesday. Write what they do when the new thing is down. If the answer is “we wait,” you have a toy. If the answer is “we lose a day,” you have a product problem.

Prototype in the open, production on a domain you own

A prototype is a test you can fail. Production is a URL, a login, a bill, and a person who can turn it off. Do not mix them. Do not call a deck a prototype. Do not call a prototype a company.

Weekly increments you can click. Acceptance is a non-engineer completing the job. You own the repo on final payment. SINLE Technologies LLC bills in USD against a written scope.

What we decline

A brochure with a new logo. A chatbot with no job. “The Uber of” a market you do not serve. If the next step is a system a company can run — with a human lock on money and sends — write.

The steps — do these in order

1. 01

   Walk the job once without talking

   Write waits, handoffs, and anything that needs a hero.

2. 02

   Ask what they already hacked

   Spreadsheets, jigs, night-shift notes. Informal tools are a map.

3. 03

   Score: frequency × pain × your right to build

   A painful rare event may not be your product. A daily wait might be.

Keep reading

• Companies

  How companies find new innovation opportunities

  Not a suggestion box. Customer jobs, internal constraints, and adjacent work you already get paid for.

• Engineers

  How engineers find problems worth solving

  Stand where the job breaks. Ignore the backlog of interesting tools. Worth is frequency, cost, and a user who will live with the fix.

• Problem to business

  How to turn a problem into a business

  A problem is not a company. Who pays, how often it hurts, and whether you can deliver without becoming the hero.