Home/Insights
InsightsWritten by the engineers doing the work, about things that happened. No gated PDFs, no email wall, no vendor byline.
Four of the eight are desktop-oriented and usually out of scope for a cloud platform. Here is what the other four actually require, and where the scope argument with your assessor will be.
Read articleAsk these in the first meeting. The answers tell you more than any capability deck — including ours. Two of them we find uncomfortable, which is rather the point.
Read articleDelete, rightsize, tier, commit, redesign, measure — in that order, because doing it in any other sequence locks in the waste you were trying to remove.
Read articleIncluding the wave that got rolled back, the two workloads we told a customer not to migrate, and the model we refused to be paid under.
Read the case studiesWe considered it and decided against. A newsletter creates an obligation to publish on a schedule, and writing to a schedule is how field notes turn into content marketing.
New pieces appear here when there is something worth saying. If you want to know when, the LinkedIn page is the only place we post them.
The engineers who wrote these are the ones who would work on your account. A conversation about a specific problem is more useful to both of us than a capability overview.
Talk to an engineer