Why I Keep a Daily Work Blog (And You Should Too)

-

Once I was pulled into an emergency meeting about a project that had stalled six months earlier. The client was asking pointed questions about decisions made during the initial planning phase, and the original project manager had moved to another company. As I sat there watching my colleague scramble through scattered email threads and half-remembered conversations, I was reminded of a practice that has saved me countless times: keeping a daily work blog.

I know it sounds excessive, but hear me out. For most of my career, I've maintained what I call my daily project log using Confluence's blog widget. I set it up right in the center of my personal workspace, surrounded by my other project notes and references. Every day, without fail, I spend five minutes documenting anything relatively significant that happened with my projects.

This isn't about writing novels or crafting perfect prose. It's about capturing the small but crucial details that slip away: why we chose vendor A over vendor B, what the stakeholder really meant when they said "make it more collaborative," or how we solved that weird integration issue that kept popping up. These seemingly minor decisions and moments add up to form the real story of how projects unfold.

The practice started almost by accident. I was managing a complex software rollout with multiple teams, and I found myself constantly forgetting the context behind decisions made weeks earlier. When team members would ask "why did we decide to do it this way?" I'd find myself giving vague answers or worse, making up reasoning after the fact. That's when I realized I needed a better system.

Now, when someone needs to step in for me or when questions arise months later about project history, everything is there. Not buried in email threads or locked in someone's memory, but clearly documented and searchable. I've watched colleagues spend hours trying to reconstruct the logic behind past decisions while I can pull up the exact reasoning in seconds.

If your company doesn't use Confluence, any blogging platform will work. The key is making sure it's accessible to your team and future project managers who might need to understand your work. You can use everything from internal SharePoint sites to simple shared Google Docs. The tool matters less than the consistency.

The real value becomes clear during handoffs and transitions. When I moved from one major project to another one year, my replacement told me the daily log was worth more than any formal documentation I could have created. It gave her the context and reasoning behind hundreds of small decisions that would have otherwise been lost.

Keeping this log has also made me a better project manager. Writing down decisions forces me to think more clearly about why I'm making them. It's amazing how often the act of documenting something reveals gaps in my thinking or helps me spot patterns I might have missed.

The practice takes discipline, but the investment pays dividends every time someone asks "how did we get here?" and you have a real answer instead of educated guesses.

Popular posts from this blog

The Dual Faces of Technology: Enhancing and Replacing Jobs

-
Image
Automation has been on my mind a lot lately, more immediately due to a book I read , but also because of the looming reality of artificial intelligence. To understand what's involved, making the distinction between replacing technologies and enabling technologies is crucial. As we traverse the timeline of the 20th century, we observe how each type of technology has distinctly influenced employment. Automated technologies have transformed industries by replacing manual labor with machines. Consider the automated switchboards introduced in the early 20th century. Previously, telephone operators manually connected calls using physical connectors on a switchboard. With the advent of automated switchboards in the 1920s and 1930s, many of these jobs were eliminated as calls were routed through electromechanical systems. Similarly, in agriculture, the introduction of mechanical harvesters like the combine harvester in the 1930s drastically reduced the need for manual labor. These machine...
Read more

The Technology Trap: Capital, Labor and Power in the Age of Automation (Book Review)

-
Image
In his compelling book, " The Technology Trap: Capital, Labor, and Power in the Age of Automation ," Carl Benedikt Frey offers a sweeping examination of the historical and ongoing impact of mechanization and automation on society. Starting with the onset of the first Industrial Revolution, Frey deftly navigates through the evolution of technology up to the modern age of artificial intelligence, presenting a nuanced view of how technological innovations have reshaped labor markets and power dynamics. Frey categorizes technological innovations into two types: enabling technologies, like the typewriter, which enhance worker productivity without displacing the labor force, and replacing technologies, such as robotic machinery in factories, which eliminate certain job roles altogether. This distinction forms the backbone of Frey’s analysis, as he explores the varying implications of each type of technology on different segments of the workforce. The book traces a historical patter...
Read more

Deputy Product Owners

-
Image
"The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner." - The Scrum Guide There are a lot of ways in which my approach to Scrum differs from what's in the official guide, and since that document refers to Scrum as 'immutable,' let's just call what I do 'Notscrum™.' In Scrum, there is only one product owner per team. That person is the sole person responsible for the product backlog, and the person who advocates for the work to be done. In Notscrum there is one product owner, but there can be multiple deputy product owners. Here's how it works. When my program at Viacom was first forming I met with the then-director of the Library & Archive group and learned that while he set the priorities on work done, the archivists were organized in three distinct areas with a team lead ...
Read more