---
title: Approach · Jensen Consulting
description: "How we work: we embed in your delivery as project managers, business analysts, and business architects, from strategy through go-live and operations support. We don't provide development services."
canonical: https://jensen.inf.br/work.html
---

# Approach — we embed in your delivery

We don't parachute in with a deck and leave. We join your project — as project managers, business analysts, and business architects — and run the delivery end to end, from strategy through go-live and the support that follows. We're a consultancy, not a software house: we direct the build, we don't staff it.

## Step 01 · Shape

We agree the outcome and where we own the work.

We start by agreeing what we're delivering and the role we'll play — project manager, business analyst, business architect, or all three. We pin down the outcome, the success criteria, and exactly where our remit starts and stops, so there's no ambiguity once the work is moving. If we don't think we're the right people for it, we say so here — before you've committed anything.

- You agree: the outcome · our role · success criteria · scope
- You commit: nothing until the scope is signed off

## Step 02 · Deliver

We run it end to end, alongside your team.

We run the delivery itself — defining requirements, prototyping the experience, managing the plan, and directing the developers or vendors doing the building. We work at the speed of the project, not above it on a status deck, and we keep scope, dates, and risks honest as they move. You see progress as it happens, and the trade-offs are made in the open — not discovered at the demo.

- How we run it: embedded with your team and vendors
- What we don't do: write the code — we direct those who do

## Step 03 · Support

Through go-live, and the running that follows.

Going live is the start, not the finish. We stay on through launch and into operations support — monitoring what matters, triaging what breaks, and feeding what you learn back into the roadmap. The product keeps improving instead of quietly drifting. And we build capability as we go, so the day we leave, your team can run it without us. We're after the next product you build together, not a dependency.

- You get: a live product · operations support · a team that can run it
- We leave behind: capability, not dependence

## The hats we wear

Three roles, depending on what you need:

1. **Project manager** (delivery) — We own the plan, the dependencies, the risks, and the vendors — and keep everyone honest about scope and dates.
2. **Business analyst** (definition) — We turn intent into requirements a team can build — process, user stories, and acceptance criteria.
3. **Business architect** (architecture) — We connect the product to the business — capabilities, systems, and the shape of how it all fits together.

## On case studies

Client work stays private. We don't publish client names or numbers. The work runs deep inside a client's product, process, and delivery — the kind of detail no team wants on a competitor's desk, and we'd rather earn the next engagement than turn the last one into marketing.

If you'd like to understand whether we've delivered something like your project, the honest way to find out is a conversation. We'll tell you plainly what we can and can't speak to: [Contact](contact.html).

---

[Home](index.html) · [Practice](practice.html) · [About](about.html) · [Contact](contact.html)