How Many CTOs?

What are common pitfalls to avoid when implementing the PR FAQ framework?

Short answer

Implementing the PR FAQ framework can be challenging if misunderstood as a detailed plan rather than a strategic tool. Avoid over-detailing and ensure it's used as a collaborative document to align team vision and strategy.

Implementing the PR FAQ framework can be challenging if misunderstood as a detailed plan rather than a strategic tool. Avoid over-detailing and ensure it's used as a collaborative document to align team vision and strategy.

Misunderstanding the Purpose of PR FAQ

One of the most common pitfalls when implementing the PR FAQ framework is treating it as a detailed tactical plan rather than a high-level strategic document. Marcelo Calbucci, who has extensive experience with the framework from his time at Amazon, emphasized that the PR FAQ is not about detailing which cloud provider to use or specifying APIs. Instead, it should focus on the overarching vision and strategy. "A PR FAQ is not a plan. It's a strategy," Marcelo noted, highlighting the importance of keeping it high-level to foster open feedback and collaboration ▶ 14:13.

Over-Polishing Before Feedback

Another mistake is over-polishing the document before circulating it for feedback. Marcelo shared his approach of presenting drafts to encourage honest feedback, saying, "even though I work my ass off to make this draft perfect," framing it as a draft invites more candid input ▶ 24:34. The idea is to ensure the PR FAQ remains a living document that evolves through team input rather than a finalized plan that stifles discussion.

Using PR FAQ Retrospectively

A PR FAQ should be created at the beginning of a project, not as an afterthought. Marcelo pointed out that writing a PR FAQ retrospectively misses the point of aligning the team from the start. The document is meant to be a catalyst for early-stage discussions, ensuring everyone is on the same page before the project kicks off. This proactive approach helps avoid misalignments and ensures that strategic decisions are well-considered from the outset.

Confidentiality and Appropriate Sharing

Maintaining the confidentiality of the PR FAQ is crucial. Marcelo explained that while the document includes a press release, it is not meant for public distribution. "Usually you don't want to share outside of that group of people," he cautioned, emphasizing the importance of keeping the document internal to avoid unnecessary conflicts or leaks ▶ 27:26. This practice ensures that team members can speak freely and contribute meaningfully to the document's development.

Starting Small and Iterating

For organizations new to the PR FAQ framework, Marcelo advises starting with a manageable project. This approach allows teams to adapt the framework to their culture and refine their processes without overwhelming the organization. "Like pick one project that is manageable," Marcelo suggested, advocating for gradual adoption and adaptation ▶ 20:42.

Encouraging Domain-Specific Critiques

When involving experts in the PR FAQ process, it's important to focus their feedback on their areas of expertise. Marcelo highlighted the potential for contention when individuals critique outside their domain, such as engineers commenting on legal aspects. Ensuring feedback is domain-specific helps refine the document effectively and avoids diluting the focus of discussions. "You have to think about what are the hard questions that you're going to be asked," Marcelo emphasized, which includes considering both internal and external perspectives ▶ 0:00.

The Value of Capturing the 'Why'

Brad highlighted a key takeaway from Marcelo's book: the importance of capturing the 'why' behind decisions. This resonates strongly with the PR FAQ framework, which encourages teams to articulate the customer value and strategic intent behind their projects. "One of the things that I think really resonated with me in the book was this notion of making sure that you've really captured the why," Brad noted ▶ 5:24. This focus on the 'why' helps ensure that everyone involved understands the purpose and direction of the project, leading to better alignment and execution.

Conclusion

The PR FAQ framework is a powerful tool for strategic alignment and decision-making, but it requires careful implementation to avoid common pitfalls. By understanding its purpose, encouraging open feedback, maintaining confidentiality, and starting small, teams can leverage the PR FAQ to foster innovation and clarity in their projects. As Brad noted, the process of working on a PR FAQ is as valuable as the document itself, providing a structured way to align on vision and strategy.