Connect the user's task with the business decision

An accessibility commitment needs a product plan, including the cost of maintaining it as customer workflows change. I ask product and finance leaders to explain the barrier being addressed, the users affected and the expenditure required beyond the first release. The value may include a task becoming possible without assistance, but that does not remove the need to consider commercial viability. We should distinguish a broad product improvement from bespoke work for one customer and price each honestly. I also want directors to understand when an apparently successful release creates an obligation we have not funded. This approach gives research a route into investment decisions. It avoids treating inclusion as a separate statement of good intentions that receives attention only after the revenue plan and engineering capacity have already been agreed for the year.

Research can exclude useful perspectives before the first question is asked. Travel, scheduling, equipment, communication preferences and the cost of somebody's time all affect who can participate. I expect a research proposal to fund those conditions and explain how consent and feedback will be handled. Payment recognises participation; it must not depend on a favourable opinion. Researchers should distinguish an observed difficulty from an assumption about an entire group, and report where the sample leaves questions unanswered. My role as CEO is to protect the independence of those findings while deciding how the company responds. I do not ask a small group to speak for every person with a similar access need. I ask whether the evidence is sufficient for the particular product decision we are about to make.

A licence agreement can look profitable if the future support promise is left out of the calculation. I work with commercial, finance, product and legal colleagues to separate the rights being sold from implementation and maintenance obligations. We examine the supported versions, customer population, duration and circumstances that would require a new agreement. A buyer should be able to understand those boundaries without discovering them only when something fails. Where a partner wants a broader commitment, the company must decide whether it can fund and operate that service. I am prepared to accept a smaller agreement when the alternative depends on unlimited future work being treated as free. The decision should include the opportunity we lose, not just the risk we avoid, so directors can assess the trade-off honestly.

As CEO and executive director, I bring management's account of the business into the boardroom. I need to make the assumptions behind that account available for challenge. A product correction, a narrower commercial agreement or an unresolved research finding should not disappear inside a general statement that delivery is on track. I ask functional leaders to explain what changed, what it costs and where another decision will be needed. Directors then have a clearer basis for oversight without taking over individual product tasks. I also distinguish my operational authority from matters reserved for the board and from professional advice that requires qualified specialists. The discipline is especially useful in a smaller software company, where personal familiarity can otherwise substitute for a careful explanation of a consequential commitment.