top of page
Innovative-Tech-Solutions-logo

Project Intelligence.

Help us understand how project reporting really works

I’m researching how project reporting really works in practice — what takes time, what gets rebuilt manually, where the process breaks down, and what project teams wish worked better.

 

This short questionnaire is for people involved in project, programme, PMO or delivery reporting. I’m interested in your most recent real experience, rather than what an ideal process should look like.

 

It should take around 10 minutes. Your answers will help shape the problems Cherry focuses on solving, and you can also opt in to a short follow-up conversation if you’re happy to share more.

What best describes your role?
Project Manager
Program Manager
PMO
Delivery Lead or Director
Executive or Sponsor
Consultant
Other
Which industry best reflects the project or reporting environment you were thinking about when answering these questions?
Banking, Financial Services & Insurance
Technology / Software
Government / Public Sector
Construction, Engineering & Infrastructure
Professional Services / Consulting
Healthcare
Energy, Utilities & Resources
Manufacturing
Retail / Consumer
Telecommunications
Education
Cross-industry / varies by client
Other

For example: project status report, SteerCo pack, executive dashboard, programme report, client update or portfolio report.

For example: Smartsheet, MS Project, Jira, Excel, P6, status updates from workstream leads, risk registers, financial reports etc.

For example: gathering updates, reconciling information from different sources, checking schedule changes, building slides or dashboards, formatting data or writing commentary.

Roughly how much of your own time did you spend on that reporting cycle? Please give your best estimate.
Less than 1 hour
1–2 hours
3–5 hours
6–10 hours
More than 10 hours

If you’re happy for me to follow up on something in your response as the research develops, you can leave your details below.

bottom of page