Project Management

Please login or join to subscribe to this thread

Project reporting for small organisations 

linkedin twitter facebook   Governance   PMO  
avatar
Anonymous

Hi, I recently ran a survey asking staff members to provide their feedback on the project reporting process. The main bit of feedback was that it felt too much like an overhead. Digging a bit deeper into the feedback there were some comments about the cadence being too frequent and that the verbal updates were just repetition of the written updates which most people in the organisation said they either sometimes read them/didn't read them at all. It was also felt like time was wasted in putting together the reports as the audience who should be reading them were not doing so. 



We are a very young organisation of only 4 years so project maturity is still in its early stages. When I started there were no project processes, almost 3 years down the line, there are processes but some staff members are resistant. I am now wondering whether I have introduced processes too quickly and scaling down the areas to be reported on and perhaps the cadence of the reporting (currently 2 weeks) would be a good idea. The problem with the former is that I think we're only reporting on the basics as it is (Phase, RAG (against time, resources, quality and scope), risks and issues and a written narrative) and reducing any further would compromise the value. Has anyone been in this position before and have any thoughts about how I can gain more buy into the process?

Sort By:
< 1 2 >
avatar
Tope Ladejobi London, United Kingdom
Jun 14, 2024 12:21 PM
Replying to Keith Novak
...
Unfortunately, this situation never really goes away. You can create the leanest simplest reporting templates and process, and it will erode over time as stakeholders want to tweak something here or there, or some new leader wants to review it in a different forum. Virtually every group I have joined has struggled with it, and part of my job as the lead has been trying to reign in all the reporting so that my team has the bandwidth to actually do the work.

I completely agree with the previous comments that you need to focus on who is the audience, and most importantly what is the intended outcome of the reporting. I would suggest mapping that out. People will always complain that they spend too much time on status. When you can show someone all the redundancy and/or status for the sake of looking busy, it can change the situation from complaining about life in an office to re-engineering the process.
Thank you so much for taking the time to read this and reply. I wish I had used this forum before. Lots of helpful insight.
avatar
Tope Ladejobi London, United Kingdom
Jun 14, 2024 7:28 PM
Replying to Frank Junior Harry
...

Firstly, having this survey means the problem is halved. I’ll suggest you have a brainstorming session with the team to also gain deeper feedback and creative ideas into what needs the reports should entail and the frequency - doing this together will increase their interest to read them consistently. To add, you’ll want to look at the mode of communication; interactive dashboard accessible to staff based on their need etc. Also note that, with time the suggestions from the brainstorming session may have to be revisited as the expected goals change.



 
 

Again, you could share the pros of building the project processes and how it’ll bode well for the team as the organization grows. I believe it could be in the form of a mini-benefit statement and I believe the resistant staff members may start loosening up.

Finally, you could share the performance metrics as the reports pinpoints possible inefficiencies and delays to help improve team performance. This will help build buy-in amongst the team.

I have actually carried out some brainstorming over the last week and it has actually been very helpful. Thank you for your comments.
avatar
Frank Junior Harry Servant Leader| Inpath Technologies Ghana Limited Accra, AA, Ghana
Jun 14, 2024 7:28 PM
Replying to Frank Junior Harry
...

Firstly, having this survey means the problem is halved. I’ll suggest you have a brainstorming session with the team to also gain deeper feedback and creative ideas into what needs the reports should entail and the frequency - doing this together will increase their interest to read them consistently. To add, you’ll want to look at the mode of communication; interactive dashboard accessible to staff based on their need etc. Also note that, with time the suggestions from the brainstorming session may have to be revisited as the expected goals change.



 
 

Again, you could share the pros of building the project processes and how it’ll bode well for the team as the organization grows. I believe it could be in the form of a mini-benefit statement and I believe the resistant staff members may start loosening up.

Finally, you could share the performance metrics as the reports pinpoints possible inefficiencies and delays to help improve team performance. This will help build buy-in amongst the team.

Great to hear Tope!
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

No matter how much cats fight, there always seem to be plenty of kittens.

- Abraham Lincoln

ADVERTISEMENT

Sponsors