Home · Method · Healthcare · Hospitality · Engagement · About · Book a discovery call

L.A.S.T DevOps

L.A.S.T DevOps is the delivery process for this fractional CTO engagement. It is ten weeks of documents, then oversight in 90-day blocks. Each step receives the previous document and produces one of its own.

• Learn — 2 weeks. Current-state value stream report. The next step receives the stream, the baseline, and three constraints.
• Assess — 2 weeks. Gap and risk assessment. The next step receives the workloads, the evidence, and the proposed decisions.
• Strategy — 4 weeks. Technology strategy. The next step receives the guiding policy, the ordered bets, and the refusals.
• Translate — 2 weeks. Engineering roadmap. The next step receives Now cards with owners and dependencies.
• DevOps — 90 days, then repeat. A board note at day 90. The next block receives its outcomes, or a decision to stop.

Learn and Assess are current-state work. Strategy locks a small set of decisions. Translate turns those decisions into a roadmap and does not reopen the diagnosis. DevOps holds the roadmap against the week the team is actually having.

Why the order is fixed

Companies often have the process on paper. Dining, intake, check-in, the deploy path. The floor does something else. Learn exists to capture the real current state of the technology organization before anyone recommends a tool.

Assess exists because a map is not yet a decision. It scores a few workloads against evidence: delivery gaps, risk, tech debt, and the build-versus-buy choices already live. That is the foundation of a technology strategy. It is both the zoomed-out landscape and the specific alignment between systems and business outcomes.

Strategy exists so organization leadership and engineering leadership share one executive view: the decisions, the goals, the metrics, and the order of the goals. Translate exists because a strategy without milestones, owners, budgets, and dependencies does not get implemented.

DevOps exists because implementation detail pulls an engineering group off the bigger picture. The block is there to clear blockers and keep the roadmap pointed at the strategy.

What the whole sequence refuses

• A vendor shortlist during the first two weeks.
• A maturity score with no business outcome attached.
• A strategy that is a catalog of projects.
• A roadmap that rewrites the diagnosis because a new stakeholder arrived with a feature.
• A fractional CTO who becomes the ticket router.

The same sequence is used in healthcare and hospitality. The pages below are the working version of each step.

Book a discovery call

The call is to decide whether this engagement fits. The answer can be no.