Ascendo

Work sat in inboxes, sheets and chat. Status lived with whoever last touched the file. Follow-up happened when someone remembered to ask.

The queue was not missing. It was split. One person had the file, another had the date, a third had the next action in their head. A busy dashboard in one of those tools did not make the week lighter.

We sat with the people who run that week. Intake, waiting, exceptions, and who actually owns each step went on paper first, including the ugly cases that never made it into a process diagram.

That map is the brief. Screens come after. If a step only existed as a habit, it got a name so it could live on the site.

Ascendo is the website for that map. The path of the work is on the page. Open, waiting or done is visible without a message to whoever last had the file.

When a step finishes, the next one is already named, with an owner. Planning is not a separate file you open after the fact. Charts and dates sit next to the work they describe.

The Blueprint put scope, screens and investment on paper before a sprint. Then short cycles, with the queue visible in the real systems every week, not in a slide.

We built around how the work already ran, so the site holds when that work changes. A generic portal that copies a product nobody asked for would have been faster to demo and useless on a Tuesday.

A site nobody else can run is not live. We left testing, a note on what to do when it fails, and a person who can run it when we are not in the room.

We keep improving it. The queue they run on stays clear as the week changes.

Queue

One website

Status

Visible without asking

Follow-up

Named owner

Planning

Same screen