The report exists to answer three questions:
- Did we help the client achieve their targets?
- How did the team perform?
- Are there any problems that need to be resolved?
The answers decide how we allocate people, who we assign to which project, and which problems we deal with first.
1What the page looks like
The report is one Notion table with a row per project. The columns are:
- Important: High, Medium +, Medium - or Low.
- Deal types: Size+, New opportunity, Enterprise or Partnership, as many as apply.
- Priority: a flame on the projects that need a decision this month.
- Client happiness, Lead rating, account rating: the three scores.
- Issues and resolutions: a relation to the log of what went wrong and what we did.
The sample above has ten projects. Two are High, two are Medium +, five are Medium - and one is Low. The four flames sit on the four most important rows.
2How to read the ratings
The write-up of this process says the ratings run from 1 to 5. The sample uses half points, and one lead rating is 0. No cell in it reaches 5. Client happiness runs from 2 to 4 and averages 3.1. Lead rating averages 2.2 and account rating averages 2.2. One month and ten projects prove little, but the pattern is plain: we rate our leads and account managers nearly a point below how happy we judge the client to be, and a 3 is a good month.
The sample does not define the points. We read them this way:
| Score | Client happiness | Lead and account rating |
|---|---|---|
| 1 | The client has raised an escalation or missed a target because of us | The lead or account manager missed a commitment this month |
| 3 | Targets met, no surprises | Commitments met, nothing proactive |
| 5 | The client expanded scope or referred us | The lead or account manager changed the client's outcome |
We read the 0 on lead rating as "no lead assigned or not rated".
3Data gathering
3.1Artifact collection
Collect the proof of work each project team delivered during the month:
- Demo materials (videos, screenshots)
- Updated project charters, documents, diagrams, and source code
- Logs of roadblocks, issues, and technical debts
From this process, we also observe and gather potential problems, both technical and managerial.
3.2Team performance
Evaluate the team's performance based on the following criteria:
- Do account managers advocate for and ensure the interests of the client?
- Do tech leads and project managers consult with the client on development matters?
- Do tech leads and project managers ensure delivery quality and effective team management?
- Assess each team member's performance and workload, to be discussed with team leads.
3.3Project priority
Assess the importance of each project based on its deal size, its potential to open new opportunities and any strategic partnership. The sample records these as the Important level and the Deal types tags. It shows no weighted formula.
4Conducting the report
Once all data is collected, compile the table with highlights for:
- Project sorting by importance: rank projects by priority and significance to our overall goals.
- Client happiness and performance ratings: rate client satisfaction, lead performance and account performance.
- Issues and resolutions logs: document each issue and the resolution we applied.
The project reports system summarizes each project's Discord traffic every month and can feed the artifact collection step. The original screenshot of this page is still available as the Notion capture.
