← Paul's Journal

If it’s not written down, it doesn’t exist.

The Importance of Clarity

Every project runs on clarity. The vision for a feature, a bug fix, or a creative campaign must be unmistakably clear to everyone involved — from marketers to creatives, engineers to stakeholders. But why? Because people can’t read minds. Without a written record, an idea drifts. Then it’s gone.

Documentation

That’s what documentation is for. It turns a thought into something someone can act on. We have plenty of tools at our disposal that can help us provide a platform to capture our ideas, requests, and feedback.

Write it so someone can act on it without coming back to you with a follow-up question. Write the what, the why, and the how. Skip the why and you’ll be asked for it later anyway.

Creativity

Someone always asks: doesn’t all this documentation kill creativity?

I believe the contrary is true. Clear documentation doesn’t restrict creativity; it anchors it. With a solid foundation, teams can innovate within set parameters, understanding their goals and limits.

Accountability and Measurement

“When it’s written down, it exists” goes beyond just bringing ideas to life; it creates accountability. Each team member knows expectations, by when, and why it matters. This written record becomes how we measure success (was the thing built right?), troubleshoot issues, and how we remember. People are forgetful. Documented goals and tasks crystalize expectations, transforming ‘I thought’ into ‘We agreed.’

Who is responsible?

Documenting isn’t one person’s job. Here’s what it looks like per role:

  • Marketers: Write the creative brief. Vision, audience, objectives, deliverables. Without it, nobody knows what they’re making.
  • Product Owners: You are custodians of product scope. It is essential to fully document the ins and outs of the product features, bug fixes, and user stories within tools like Jira. Your documentation is the definitive guide for what needs to be accomplished and why.
  • Technical Architects: You are responsible for the technical roadmap. You must maintain comprehensive and up-to-date architectural diagrams and technical specifications that align with the project’s goals. This ensures all team members understand the project’s underlying structure and integration points.
  • Project Managers: You are charged with being the project’s unified consciousness. You should log essential decisions, meeting notes, and risk events so they can be discussed and remembered. Don’t become a journalist.
  • Creative Roles: You play a critical role in documenting our projects’ visual and experiential aspects. Use tools like Figma to add detailed functional comments to your UI and UX designs. These annotations should clarify your design choices and the reasoning behind each decision. Such documentation ensures the strategic vision remains clear and consistent across all teams involved, particularly during handoffs or iterations. Also, remember to name your layers thoughtfully—these names provide additional context and can be crucial for understanding the structure and intent of your design. In your role, a good prototype says more than 1000 words.
  • Everyone else: You know something the others don’t. Write it down.

Concluding

Write it down and you stop having the same conversation twice.

So, the next time you have a great meeting or a brilliant idea, remember: if it’s not written down, it doesn’t exist.