Stakeholders

このコンテンツはまだ日本語訳がありません。

The stakeholder register lists the people and organisations who genuinely bear on the project. You rarely add stakeholders by hand — people arrive on their own as communications come in, and you promote the ones that count.

Where stakeholders come from

People are created automatically as emails are processed:

People on an email. When an email produces at least one register item, the people on it (From, To and Cc) are added — but only those who appear with a real display name. Bare addresses with no name, and automated senders (no-reply, mailer-daemon, task-tracker addresses, and the like), are skipped. They’re matched by email address, so the same person isn’t added twice. These arrive as contacts, waiting for you to promote them.
Sender signatures. When the classifier reads a signature block on a substantive email, the sender’s role, organisation and phone are added to their record.

Anything you declare goes straight into the register as a stakeholder: importing an action with an owner email, seeding a starter list (see Import your data or the Import button on this page), or adding a person by hand. Each stakeholder’s detail page lists the emails they appeared in.

The same person seen under more than one address is kept as one stakeholder, and their detail page shows every address they’ve been seen under, with one marked as primary.

Editing phone numbers

Signature scraping can leave a stakeholder with a pile of stale numbers. Open the stakeholder’s edit panel to curate the list: add, remove and reorder phone numbers, and mark one as primary. Duplicates are trimmed automatically.

Merging duplicates

If the same person exists as two records (say, under two email addresses that were never seen together), the duplicate review queue offers them as a merge candidate — open Duplicates from the project sidebar, review the pair, and choose Merge or Keep separate. Merging combines the addresses and history onto one record.

Narrowing the register

Above the table sit search, sort and a filter bar: Power, Engagement, Organisation, Last seen, plus the Key and Archived toggles. Organisation is a dropdown of the organisations actually present in your view of the project. Ticking rows offers Demote to contacts in bulk — the way to prune a register that has grown too broad.

The engagement grid

A stakeholder can carry a power (influence) and interest rating, each on a 1–5 scale, shown together as power × interest. From those two numbers the project derives an engagement strategy (ratings of 4 or 5 count as “high”):

	Low interest	High interest
High power	Keep satisfied	Manage closely
Low power	Monitor	Keep informed

You can set a strategy explicitly, but it is re-derived from power × interest whenever either of those is changed. If a stakeholder has no power or interest set, no strategy is shown.

Power, interest and strategy aren’t edited from a form on this page — set them by importing a register that includes those columns, or by telling the project in chat (for example, “John Smith is the sponsor with high influence”).

Linking a stakeholder to a workspace user

A stakeholder is a person in the project record; a user is someone who signs in. Linking the two is what lets action items show up as that person’s work — work is assigned through this link.

ddx PMO links automatically when a stakeholder’s email exactly matches a verified email on a workspace user’s account, and only when exactly one user matches. On the stakeholder’s detail page you can also:

Link a user by hand (a “pinned” link).
Unlink, which both removes the link and turns off auto-matching for that stakeholder (shown as auto-matching off).
Re-enable auto-matching afterwards.

A linked stakeholder shows a User badge in the list and a Workspace user badge on their detail page.