Context

Throughout my 12-year design career, reports were part of the process — sometimes mandatory for progress monitoring — but they always felt mechanical and exhausting. Yet they're important for ensuring a project stays on track, providing clarity on daily activities and their impact on the project. From my work experience:

• Your manager guides you, sometimes micromanaging by asking what's on your plate, how much you've finished, when you'll complete each task, and more.

• Once a quarter, you fill out tons of forms and answer dozens of bizarre questions about your mental state and engagement.

Does this seem familiar? This cold corporate approach is replicated from company to company without logical justification — it's for control. I doubt anything good will come from this approach. Strangle collar.

Direction

I can bet that reports aren't so bad. In fact, they will help you improve your work and boost your career. Here's how you can create a positive reporting experience:

Change Direction — Instead of waiting for your manager to ask for updates, create your own reporting channel. Set up a dedicated space in your team messenger (Slack or Discord) and write daily reports on your workload and progress.

You take the lead instead of waiting for instructions, then show your manager to confirm you're on the right track. Bonus: you cut down on sync meetings with your manager.

Create Structure — Your report should be clear and easy to skim. Avoid a random reporting style, this adds complexity. Here's my approach, but feel free to customize the structure for your needs:

• Today tasks list
• What went well list
• What went wrong list
• Tomorrow tasks list

By telling your manager what current status on your project, what works, what doesn't, you direct them. You take greater ownership over your projects and your career.

There are clear benefits for a business, allowing managers to spend more time on higher — leverage tasks instead of following up with reports or tracking down work.

Efficient, responsible individual contributors who quickly operationalize solutions are more likely to be promoted, invested in, and trusted with key projects.

Origins

From childhood, we've given reports with our first responsibilities—cleaning our rooms, completing chores, and reporting to teachers and parents on homework. As we grow older, our reports become more complex, but our reporting habits develop early. Back in the day, I hated homework. Actually, it caused me many problems, and as I discovered, this is not a rare case.