Technology has to earn its place.

Begin with the inconvenience

There is an easy way to start a technology project: choose a tool and look for somewhere to use it. There is a more useful way: find a recurring inconvenience and understand it properly. The second approach is less glamorous at the beginning, but it gives the work a purpose.

Perhaps an enquiry arrives in one place and has to be typed into another. Perhaps a customer explains the same request three times. Perhaps a team cannot tell whether a quote has been followed up. Each problem is small enough to overlook and concrete enough to investigate.

Before deciding that software is the answer, ask how the work happens now. Who does it? What information do they need? Where does the process become uncertain? A tool cannot resolve a decision nobody has made.

Less friction, not more machinery

A system can look sophisticated in a demonstration and still make an ordinary day harder. If it needs duplicate records, adds unnecessary steps or hides important information behind a new screen, the team may understandably work around it.

That is not always resistance to change. It can be evidence that the proposed change has misunderstood the job. Useful technology should reduce the effort needed to do something well. It should also make it clear when a person needs to intervene.

A good initial test is modest: choose one real workflow, agree what better would look like and observe the result. Fewer missed handovers may matter more than the number of features launched.

The thinking behind Bridge-iT

Bridge-iT is Brian Nangle’s venture in development, exploring AI-assisted sourcing through WhatsApp. The idea begins with a familiar exchange: someone needs something, and a suitable supplier needs enough information to decide how to help.

The ambition is to turn that request into a clearer opportunity for the right supplier. It is an example of the kind of question Ironbridge finds interesting: can technology make an existing interaction more useful? The venture is still in development, with that question at the centre of the work.

Keep people in the picture

Efficiency is not the only consideration. People need to know what has happened, whether information is accurate and who is responsible for the next step. Automating a message is not the same thing as taking responsibility for the promise inside it.

Our view is that technology should support judgement and dependable service. Start with a real need. Make a focused change. Learn from what happens. Keep the parts that genuinely improve the work. That is a quieter ambition than transforming everything at once, but a more useful one to build around.

Before introducing a tool, try describing its job in one sentence without naming the software. If that sentence is difficult to write, the problem may need more thought. If it is clear, the team has something concrete against which to judge the result.