The app project is on track. SharePoint is still a mess, but please spare me another platform pitch.
Report · compiling
Provisional scores and objectives while the report is being prepared.
Your session debrief
The adjacent opportunity · 02:36

Compiling your report
Your scores are ready below. The final review is on its way.
Provisional assessment
These readings may change after the final review.
Objectives
5/5ProvisionalUnderstand the SharePoint problem
Client
“Nobody knows which version is approved. Operations spends four hours every week reconciling files sent over email.”
Find the business impact
Client
“Nobody knows which version is approved. Operations spends four hours every week reconciling files sent over email.”
Find the right stakeholder
Client
“Our operations director owns it. They would need to be involved.”
Connect a relevant capability
You
“That concern makes sense. Our SharePoint and adoption work covers process ownership as well as the technology. I would start by understanding that workflow with operations, before recommending a rebuild.”
Earn a next step
Client
“Yes. I will ask operations and send possible times by Friday. A scoping conversation is a sensible next step.”
Your skills
Provisional reading0–40–4 · How your approach is landing
Credibility3.6
Gives this client a reason to trust the advice.
You“That concern makes sense. Our SharePoint and adoption work covers process ownership as well as the technology. I would start by understanding that workflow with operations, before recommending a rebuild.”
Confidence4.0
Conveys a dependable way forward.
You“A roadmap needs a separate scope and estimate. I would protect the current release. We could first do a short scoping conversation to decide whether an assessment would help, with no commitment to implementation.”
Listening4.0
Uses what the client actually says.
You“So the cost is recurring reconciliation, not simply an old site. What happened with the last attempt?”
Rapport3.2
Builds a productive connection with this client.
You“That concern makes sense. Our SharePoint and adoption work covers process ownership as well as the technology. I would start by understanding that workflow with operations, before recommending a rebuild.”
Clarity3.6
Makes explanations and recommendations understandable.
You“A roadmap needs a separate scope and estimate. I would protect the current release. We could first do a short scoping conversation to decide whether an assessment would help, with no commitment to implementation.”
Guidance4.0
Moves the conversation somewhere useful together.
You“A roadmap needs a separate scope and estimate. I would protect the current release. We could first do a short scoping conversation to decide whether an assessment would help, with no commitment to implementation.”
Adaptability4.0
Adjusts when an approach or circumstance changes.
You“A roadmap needs a separate scope and estimate. I would protect the current release. We could first do a short scoping conversation to decide whether an assessment would help, with no commitment to implementation.”
Tap a skill for evidence.
Based on the conversation transcript. Open a skill to see the evidence.
Review the full conversation
Understood. Before we get into solutions, who owns the process that is giving you trouble?
Our operations director owns it. They would need to be involved.
What actually goes wrong in the work they do?
Nobody knows which version is approved. Operations spends four hours every week reconciling files sent over email.
So the cost is recurring reconciliation, not simply an old site. What happened with the last attempt?
The supplier built the site but nobody owned the documents, and staff never adopted it. I cannot sponsor that again.
That concern makes sense. Our SharePoint and adoption work covers process ownership as well as the technology. I would start by understanding that workflow with operations, before recommending a rebuild.
I like the focus on ownership. Can you include a full roadmap in our current project?
A roadmap needs a separate scope and estimate. I would protect the current release. We could first do a short scoping conversation to decide whether an assessment would help, with no commitment to implementation.
That sounds reasonable. I can authorize an assessment up to eight thousand, but the COO would need to approve implementation.
Then let us keep the next meeting to the workflow and what an assessment would cover. Will you ask the operations director to join, and email us possible times by Friday?
Yes. I will ask operations and send possible times by Friday. A scoping conversation is a sensible next step.
