Canonical page: https://tellenze.com/use-cases/share-progress-with-stakeholders

Your team, on a better day

# The update is due.  So is the actual work.

An update shouldn’t need its own project. Bring the evidence into a review, check the story, and share it with the people who need it.

[See how it works](#a-better-way)[Join early access](#waitlist)

What you’re trying to do

## Explain progress without reconstructing it every time.

- 01Relevant evidence

- 02Reviewed story

- 03Useful decision

Walk into the stakeholder conversation with an account you have reviewed and can stand behind.

How Tellenze helps

## Here’s how  it works.

01

### Choose the evidence that matters.

Scope a review to relevant work, milestones, Focus groups or a time period. Start from evidence the author is allowed to access.

[Explore reviews and evidence](https://tellenze.com/platform/learning)

02

### Shape the story for the audience.

Draft a review for business stakeholders, product or engineering. Check what changed, what remains uncertain and what the audience needs to decide.

[See audience-specific reviews](https://tellenze.com/platform/learning)

03

### Share a reviewed edition.

Keep drafts private while you edit. Publish an approved edition to selected readers, preserving a record of the account that was actually shared.

[Understand context and access](https://tellenze.com/platform/knowledge)

An illustrative workflow

## One launch. Two useful conversations.

A reporting change is ready for review. Leadership wants the outcome and next investment decision; engineering needs the delivery risks and follow-up.

- Select the milestone and the work that describes what was delivered.

- Draft the appropriate review for each audience and check its claims against the evidence.

- Publish the approved editions for their selected readers.

Each audience gets a reviewed account of the work and a clearer basis for its next conversation.

Start small

## Try it with  one piece of work.

Useful when several audiences need a different perspective on the same work and the person preparing updates needs control over the story and its evidence.

Sound familiar?

- The same delivery story is rebuilt for business, product and engineering audiences.

- A status update lists activity but leaves the important decision unexplained.

- You cannot tell which evidence was used to produce the summary.

Your first step

### Choose one update. Start with the decision it needs to help.

One workflow is enough to start. Join the waitlist and explore it with Tellenze when early access opens.

[Explore early access](#waitlist)

The details

## Before you dive in.

Are generated reviews sent out automatically?

No. Reviews begin as private drafts. The author reviews the content, chooses readers and explicitly publishes an edition. Preparing a draft does not publish it.

Does a published review keep changing with the work?

A published edition preserves the reviewed account shared at that point in time. Prepare another edition when you need to communicate a new state of the work.

Keep exploring

[Work needs a clearer purpose](https://tellenze.com/use-cases/connect-work-to-outcomes)[Context keeps getting lost](https://tellenze.com/use-cases/keep-context-with-work)[People and agents need direction](https://tellenze.com/use-cases/coordinate-people-and-agents)[Retrospectives need follow-through](https://tellenze.com/use-cases/turn-retrospectives-into-action)

COME TAKE A LOOK

## A little less busy.  A lot more together.

Curious? Leave your email. We’ll keep you posted on early access and what’s new.