# Access to a product is not yet value.

All stories are fictional. They do not describe specific people, companies or projects. Any resemblance is coincidental.

The client has the service, but employees continue working as before. Some lack data; others do not know when to use the new tool. Meetings focus on features, while the client expects a change in day-to-day work.

## Where we could start

I would establish which work the client wanted to improve and where difficulties arise now. I would identify the first useful check: initial use, obstacles or expectations of the result.

## What you would have

A review of the path to useful adoption and an agreed first investigation.

## Participants

The client, users, product and support as needed.

## Roles and decisions

Relevant specialists perform technical work, configuration and specialist measurement.

## Factual experience, separate from the fictional story

MVP Lab / Pivot: Client requirements, approvals, demonstrations and release review.
https://apiperson.com/experience/#work-pivot

[The client has not started using it](https://apiperson.com/clients/value/not-started/)

[People started, but cannot complete the task](https://apiperson.com/clients/value/blocked/)

[It is used, but the expected benefit is unclear](https://apiperson.com/clients/value/effect/)

[Book a 30-minute call](https://calendar.app.google/4FrxQkHkAZ32PkzA9)

mailto:apiperson.com@gmail.com