By week four, the page was a ghost town. The last comment read: “We’ll just talk offline.”
Week one went well. People typed. Maya slept.
Maya felt the familiar slide toward chaos. But instead of chasing people, she did something desperate. She opened the template’s “Retrospective” section—the one nobody uses mid-project—and wrote: The template isn’t the work. The template is a lie we tell ourselves so we feel safe. The work is the messy, human, terrifying act of admitting when we’re stuck. She shared the page one last time, with no agenda, just that note. project management confluence template
By Friday, the template was uglier but alive. People had struck through outdated assumptions, added emoji reactions to risks, and turned the “Decisions” log into a surprisingly honest debate thread.
“Everything is in Confluence,” Maya announced, projecting the template onto the wall. “Status updates every Thursday. Decisions logged in the table. Risks go here.” By week four, the page was a ghost town
Silence for an hour. Then Leo added a comment: “API is failing at 30% probability now. Actually 60%. I didn’t want to type it because I thought you’d make a ‘process’ to fix it.”
Priya wrote: “Marketing’s timeline slipped two weeks. I hid it in a private doc.” Maya slept
She populated every blue-highlighted placeholder. She linked the Jira epic, attached the RACI chart, and even filled out the “Definition of Done” section—a field most treated as a suggestion box.
