Ironwood Operational software for airports and air navigation — movements, billing, parking, permits, compliance — has earned the same bad reputation ERP earned decades ago: expensive, drawn-out, and short of the promise. The reason is almost always the same. Software selection gets more attention than business-purpose formulation. The most consequential decisions are made before anyone sees a demo. Here are ten questions to answer first.
1. What is limiting your airport's growth and competitiveness?
It comes down to three things: fast, actionable information; the agility to act on it across the whole aviation value chain — airlines, handlers, the ANSP, the regulator, the municipality — not just inside your own fence; and automation and flow through the operation. What is actually stopping you from having these?
2. What behaviours and rules created those limits?
Usually: bureaucracy built to shift accountability rather than serve the operation; KPIs that reward silos over integrated outcomes; inward-looking thinking instead of your role in the wider network; and measuring efficiency (were the staff busy for eight hours?) instead of effectiveness (what did the airport actually achieve?).
3. How will the investment overcome those limits?
Make overall effectiveness the project's success criterion. Understand what the solution must do before you decide what to buy — and before you ask an integrator for a fixed price. Keep ownership of the improvement; don't outsource accountability to a vendor. Align KPIs to airport-wide effectiveness, not personal scorecards.
4. How current and accurate are your processes, rules and data?
Operational systems are living things; the documents describing them are not. Airport master data especially — aircraft, operators, tariffs — drifts the moment a key person leaves, and quietly turns into lost revenue and failed audits. Start by genuinely understanding how the airport works today, in a proper process model — not a slide deck.
5. What new rules and behaviours will take the airport forward?
Think effectiveness, not busyness. Think about your place in the network. It is all about information and how fast you respond to demand. Let business purpose lead the requirements — not what the old system did, and not the feature list of the new one. Remember: salespeople are rewarded for selling software, not for improving your airport.
6. How must the software support those new rules?
Root the design in purpose, not in a copy of the old system. It must deliver fast, accurate, actionable information; let decisions land quickly and consistently across the operation; improve flow across the whole value chain, not just one department; and be judged on benefits realised, not only on deadlines and budget.
7. Who are your real stakeholders — inside and out?
Airports never operate in isolation. Airlines, handlers, fuel, the ANSP, the regulator and the municipality — upstream and down — are all stakeholders in flow. Internally, that includes finance, audit, risk and compliance, not just operations.
8. How will you keep them consulted, involved and empowered?
Consulted (ask their advice). Collaborated with (build it together). Informed (share accurate, unfiltered information — it breeds trust). Involved (part of the team). Empowered (actually able to effect change). One shared objective across staff, partners and vendors.
9. What will it do to the airport and its people?
Every operational-software project ends on one of four paths:
- Effective — returns far outweigh the spend; limitations shrink; the future looks exciting.
- Efficient — the team hits time and budget, scope was quietly cut, and the airport is no better off. You might as well not have done it.
- Precipice — the point of no return, where going back hurts more than paying to finish.
- Fail — cancelled, lawyers engaged; money, time and good people wasted.
Only the first is worth starting.
10. How do you know the airport is ready?
Surface the non-negotiables, the fears and the hopes up front, and find the compromises early. Consider a project code of conduct everyone signs. Ask whether your own bureaucracy will support the change or block it. And do scenario planning before project planning — name the flags that signal a scenario is unfolding, so you recognise them and act before they become surprises.
Notice that these ten questions have almost nothing to do with software, and everything to do with purpose. That is the point. The airports that get value from technology are the ones that knew what they were trying to achieve before they shortlisted a product.
We built Ironwood Aero to the same discipline: purpose first, the operation's real value chain in mind, benefits realised — not features sold.