Line of Sight: from value driver to the work that delivers it
AtlanticM&A5 min read
Line of Sight is how AtlanticM&A traces every value driver down through its charter objectives to the work and risks delivering it, and shows you where that thread breaks.
"Why is this task in the plan?"
Sooner or later a steering committee asks some version of that question. The honest answer is a thread: this piece of work delivers an objective, and that objective serves one of the value drivers the project exists for.
On most programmes that thread is drawn once, on a slide, near the start. Then the plan moves and the slide does not. By the time someone asks the question, the slide answers a plan that no longer exists. In AtlanticM&A the thread is kept in the plan itself, so it moves when the plan moves.
Where the thread starts
It starts on Strategic Direction, the first of the four planning surfaces. You state what the deal or programme is for, and that becomes value drivers and objectives, with proposed workstreams to carry them. You can write it yourself, or give it a short brief and let the AI draft it. Every suggestion arrives as a proposal you accept or dismiss.
Push to Charters then puts the same objectives on the matching workstream's charter. The app describes this as "one row, two windows": an objective is a single record, seen from Strategic Direction and from the charter. If a workstream adds an objective of its own on the charter, it files back to Strategic Direction as Uncategorised, for someone to place.
A project with no Strategic Direction still works. It just has no line of sight from thesis to task.
Down through the charter to the work
On the charter, the path to "Complete" is a list of deliverables grouped under the project's phases or named initiatives. Some of those deliverables are flagged as milestones, and here the rule is strict: only a milestone can carry an objective, and each objective sits under exactly one milestone. Everything else becomes an ordinary task when you push to the work plan.
The milestones guide makes the same point from the plan's side. When you set a milestone, say which objective it delivers, "so the line of sight from deal thesis to dated commitment stays intact."
Not every task has to serve an objective, and the charter says so. Some work is hygiene: "Necessary work that serves no stated objective. Normal, and not a gap." It stays unmarked. I think that matters. A traceability feature that forces every task to claim a strategic purpose teaches people to invent one.
Where it breaks
The Line of Sight view sits on the Charters page, alongside the other views of the whole programme. For each value driver it shows the objectives assigned to it, and under each objective the milestones, tasks and risks linked to it.
The gaps are named in plain words:
- "No objective owns this driver": strategic intent that no workstream has picked up.
- Objectives not linked to a value driver.
- "No linked work or risk yet", on an objective with nothing under it.
An objective that no workstream has taken up yet is marked "Not yet adopted". That is where a thread starts, rather than where one breaks, so it is not flagged as a gap.
At the foot there is one plain count: how many of the value drivers are traced to execution. The view does not score the plan or recommend anything. It shows where the thread breaks, and the people running the programme decide what to do about it.
On the work itself
You do not have to open the charter to see the thread. With Line of Sight switched on, each item on the work plan and in the risks and issues log carries a small chip naming the value driver and objective it serves. Switch it off and the chips go. The full thread, and where it breaks, stays on the charter.
Because milestones live inside the plan, moving one moves everything that reads it: the roadmap, the project dashboard and the charter, and the next steering committee or board pack from Report Centre reads the same record. That is the reason for keeping the thread in the plan rather than in a separate deck. The reporting comes out of the work, so it cannot drift away from it.
About AtlanticM&A
AtlanticM&A is the Agentic Transformation OS. Its agents work inside the programme, both augmenting and automating the work of the transformation team: work plans, governance, stakeholders and reporting in one place, with a live value bridge that moves as the work does. It is a system of work rather than only being a system of record: the charter is written in it and the plan is built in it. Meeting notes come back as proposed updates to the plan and the RAID log, the team decides what stands, and every change the AI makes carries an audit trail. The platform does the slide-building, status reporting and stakeholder briefings that usually keep a consulting pyramid busy, so a small senior team can run the programme more nimbly and for less.