Technology decisions
Decide what must stay easy to change before choosing a platform.
Identify the business choices most likely to move, then test how safely and practically a proposed platform can accommodate them.
A hypothetical services business is choosing a new operations platform. Every shortlisted product supports today’s workflow. The harder question is what happens when the business adds a region, changes its pricing rules or connects a different customer channel. A platform decision should cover the work you need now, but it should also make the most likely changes visible before the contract and implementation create momentum.
Name the decisions that are likely to move
Start with business choices rather than a general request for flexibility. Which parts of the operating model could reasonably change during the life of the platform? Look at products, prices, approval rules, customer channels, reporting needs, suppliers and organisational structure.
Do not attempt to predict every future requirement. Select the few changes that would be expensive or disruptive if the platform made them difficult. Record why each one matters and who would own the decision. This gives suppliers and internal teams something specific to test.
- A new service or product needs a different workflow.
- Pricing or approval rules vary by customer or region.
- A supplier, data source or customer channel is replaced.
- Reporting responsibilities move between teams.
- The business needs to retrieve its data and leave the platform.
Test a change, not just the current process
Choose one plausible change and ask each shortlisted supplier to show how it would be handled. Use the same scenario and representative synthetic information so the comparison is fair. Observe which parts can be configured by your team, which require specialist support and which depend on custom development.
Ask what happens to existing records, permissions, reports and integrations when the change is made. A convincing demonstration of the new screen is not enough if the surrounding process must be rebuilt or historical information becomes difficult to use.
Turn broad claims into evidence
Words such as configurable, open and scalable can describe very different realities. Translate each claim into an observable question. Who can make the change? How long would it normally take? Is it covered by the subscription, professional services or a separate partner? Which documented limits apply?
For integrations, identify the information that can be read or updated, the controls around access and the behaviour when the connection fails. For data portability, inspect a representative export and confirm whether relationships, identifiers and useful history are retained. State what has not been tested rather than treating a supplier statement as verified evidence.
Make reversibility part of the decision
Add change effort and exit conditions to the decision alongside capability, cost and implementation time. This does not mean choosing the least committed option. It means understanding where the business will retain choice and where it is deliberately accepting a dependency.
Record the most important assumptions, the evidence used and the conditions that would trigger a review. Revisit them when the operating model changes, a major extension is proposed or supplier terms materially alter. A platform can remain the right choice while the reasons for that choice evolve.
Rethink’s technology second opinion can challenge a proposed platform decision before commitment. If the work proceeds, longer-term delivery support can help keep the original decision, changing business needs and implementation choices connected.