Five questions we ask before recommending a platform investment

Platform investments — internal developer platforms, service meshes, observability stacks, golden path tooling — are easy to advocate for and hard to scope. We use a short list of questions during retainer kickoffs to keep the conversation grounded.

First, who actually feels the friction this investment is supposed to relieve? If the answer is "platform leadership," we slow down. If the answer is "five named product engineers we can talk to," we keep going.

Second, what would a one-quarter pilot look like, and what would success even mean at that scope? If the answer requires a new vendor contract before the pilot, that is usually a signal to redesign the pilot.

Third, what does the team commit to retire if this investment proves out? Net-new tooling without a retirement plan tends to compound the friction it was meant to relieve.

Fourth, who owns this on day 365? "The platform team" is not an answer. We need a name and a job description.

Fifth, what is the smallest thing that would prove this is a bad bet? Teams that can answer this quickly are usually closer to ready. Teams that cannot are usually too early.

These are not gates. They are conversation prompts. But they have saved more than one engagement from drifting into a year-long investment that was not yet warranted.