Define the project
Agree the problem, scope, stakeholders and intended outcome. Turn an initial idea into a brief people can challenge and approve.
In development · For Microsoft Teams
Define the work.
Plan the
change.
AI support for projects, requirements and business change.
Assisted Review is being developed for Microsoft Teams: a place to understand the problem, agree what is needed and prepare a practical plan—with the evidence and decisions carried forward.
ARTHE PROJECT, HELD TOGETHERCLM
Project / CLM reviewWhat needs
What needs
to change?
Review the process, people and platform.
A problem grounded in evidenceTrace the friction in contract approvals.
01Requirements people can agreeNeed, priority, owner and acceptance criteria.
02A change plan ready for reviewActions, responsibilities and adoption.
03Next conversation.
Same project.
Illustrative concept · not a live product screen
Better decisions.
Practical change.
Understand the problem.
Agree what is needed.
Prepare people for change.
01 / The approach
From an open question
to work people can act on.
Use AI to organise evidence, challenge assumptions and develop the documents a project needs. Start with the help you need; these capabilities can be used independently.
Understand the current state
Bring together interviews, documents and process evidence. Distinguish observed problems from assumptions and missing information.
Develop requirements
Turn needs into clear requirements, with sources, owners, priorities and acceptance criteria. Surface conflicts for people to resolve.
Compare the options
Assess changes to processes, roles and systems against agreed criteria. Draft a recommendation with its evidence and trade-offs.
Plan the change
Identify affected teams, dependencies and responsibilities. Prepare a plan for communication, training, rollout and checking the result.
Review and continue
Review drafts, record decisions and assess new change requests against the agreed scope. Return to the current position and next actions.
Designed for analysis and change planning. The intended outputs are briefs, requirements, recommendations and change plans. Software development and code implementation sit outside the product’s scope.
02 / Worked example
A CLM review.
From friction to a plan.
A contract lifecycle management (CLM) review looks at the process, people and platform. Follow an illustrative legal operations project, starting with unclear ownership of contract approvals.
YOU, IN TEAMS
“People keep chasing contract approvals. Help us work out what needs to change.”
AR
Start with the workflow and the evidence.
Review intake and approval steps with Legal, Sales and Procurement. Check sample requests before concluding whether the problem is ownership, process or the platform.
DRAFT REVIEW BRIEF
Working hypothesis: requesters cannot see who owns the next approval.
Evidence needed: stakeholder interviews, workflow records and examples of requests that stalled.
FOR REVIEW
Project brief and current-state assessment
Scope, stakeholders, evidence gaps and a proposed measure: time waiting for approval.
YOU, IN TEAMS
“The interviews point to missing approval visibility. Turn that need into a requirement.”
AR
Describe the need so people can agree it.
Link the requirement to the interview finding. Ask Legal Operations to confirm its priority and check the proposed acceptance criteria with requesters.
DRAFT REQUIREMENT · REQ-04
Need: an authorised requester can see the current approval stage and responsible owner.
Acceptance: using a sample in-progress request, the requester can identify both without contacting Legal.
FOR REVIEW
Requirements register
Source: interview finding · Proposed owner: Legal Operations · Priority: to agree.
YOU, IN TEAMS
“Can we meet that need with our existing process and platform?”
AR
Compare routes against the requirement.
Consider clearer process ownership, reconfiguring the current platform, and extending or replacing it. Compare coverage, cost, effort and adoption needs against the agreed criteria.
OPEN QUESTION · REQ-04
Check: can the current platform expose the approval stage and owner to authorised requesters?
Decision needed: confirm capability and cost before choosing a route. No option is approved yet.
FOR REVIEW
Gap analysis and options appraisal
Evidence, assumptions and trade-offs, with a recommendation once the gaps are resolved.
YOU, IN TEAMS
“If we choose to improve the existing workflow, what would the change involve?”
AR
Prepare the people and the handover.
Draft responsibilities, communications and training for requesters and approvers. Define a pilot, the checks for REQ-04 and the decision to proceed with a wider rollout.
DRAFT CHANGE PLAN
People: agree approval ownership and train a pilot group to find the status of their requests.
Check: validate REQ-04 with users and compare time waiting for approval with the baseline.
FOR REVIEW
Change plan and delivery brief
Impacts, actions, owners, acceptance checks and rollout decisions for the delivery team.
Illustrative concept, not a live product demo or customer case study. Each capability can also be used on its own.
03 / Optional, when the work gets complex
Map the work
ahead.
See what can progress, what is missing and where a decision is needed.
A planned work map would connect questions, evidence, requirements and decisions. In the CLM review, a platform question may hold up an option while stakeholder interviews continue.
Use a map when the project needs one. Keep simpler tasks simple.
CLM REVIEW / WORK MAPILLUSTRATIVE
?How should we improve approval visibility?
REQUIREMENT DRAFTED
Stage and owner visible
REQ-04 links the interview finding to a proposed acceptance check.
EVIDENCE NEEDED
Can the platform support it?
Confirm requester access, capability and cost with the platform owner.
Choose a route for change
Depends on validated requirements, platform evidence and stakeholder approval.
Meanwhile: continue interviews and draft the change impacts.
04 / Designed for continuity
Return to the project.
Keep the reasoning.
The intended project record brings together findings, requirements, decisions and drafts. When a new request arrives, assess its effect on the agreed scope and plan.
A shared project record
Return through Teams to the current brief, open questions and next actions. Continue the CLM review without reconstructing earlier conversations.
Traceable requirements
Connect a stakeholder need to a requirement, a decision and an acceptance check. Keep sources and assumptions visible as the work changes.
Decisions stay with people
Stakeholders agree priorities, approve requirements and choose the route. AI prepares and challenges the work; a draft remains a draft until reviewed.
Help shape what comes next
Bring a project.
Work out what’s next.
Assisted Review is in development. If you are reviewing a CLM platform, gathering requirements or preparing a business change, let’s explore a focused pilot around a real project.
Discuss a pilotContact Barry Rodick on LinkedIn. Opens in a new tab.