Pondering public relations as project management
Update: Embedding public relations with clarity, candour and no-pants humour has now published in the Journal of Professional Communication, Volume 3, Issue 1 (2013).
Later in November 2013, my submission for The Journal of Professional Communication (JPC) publishes, which is an “ideas” review of Scott Berkun’s fifth book, The Year Without Pants: Wordpress.com and the Future of Work.
Scott Berkun describes his 21 months of working at Automattic as “participatory journalism.” My JPC take is that in many ways it is a new-form style of corporate media, a transparent and honest, embedded insider’s take or “creation” regarding the organization narrative—hence how I qualify it as a public relations initiative, even if this wasn’t the intention or couched in those terms by the author.
Berkun’s narrative includes an appreciation for Automattic’s unique culture and values based on “passion and joy” for work, which stems from the company’s still-young, highly principled founder, Matt Mullenweg, plus ideas about being a data-influenced culture, rather than a data-driven one, and how a collaborative culture does have some negative side effects, such as a lack of creative friction and some apprehension to speak truth to power. In other words, being risk averse at the expense of persuading towards even bigger, innovative ideas.
In comparing Automattic to the Melbourne Mandate, including its Professional Development Wheel that Catherine Arrow developed for the Global Alliance, I was struck by how this company could be a best practices case study.
This post on PR Conversations focuses on a couple of relevant and interesting “project management” ideas that I believe correlate to public relations and communication management, as well as some PM terms new to me.
Length, not value, precluded me from including them in the JPC article.
Building focus and trust into the communication process
One of the first ideas I warmed to is the concept of building the end communication into the front part of any given project, in order to bring simplicity and clarity, i.e., focus, into the equation. I’ve become increasingly less fond of the term “messaging” that gets thrown around regarding corporate communication, let alone the stereotype of public relations being mainly about spin.
I don’t know of any company that begins to write its news releases or website copy so early in the game before something is launched (or “shipped”)—do you?
I’ve extracted much of this passage about Workflow at Automattic, which demonstrates how close to the conceptualization stage is the first draft of the end communication (i.e., step #2). Italics are mine:
- Pick a problem. A basic problem or idea is chosen, i.e., “It’s too hard to print blog posts” or “Let users share from WordPress to Facebook.” …After an idea is chosen, discussion begins on how it should work.
- Write a launch announcement and a support page. Most features are announced to the world after they go live on WordPress.com. But long before launch, a draft launch announcement is written. How can you write an announcement for something that doesn’t exist? The point is that if you can’t imagine a compelling simple explanation for customers, then you don’t really understand why the feature is worth building. Writing the announcement first is a forcing function. You’re forced to question if your idea is more exciting for you as the maker than it will be for your customer. If it is, rethink the idea or pick a different one.
- Consider what data will tell you it works. …The plan for a new feature must consider how its positive or negative impact on customers can be measured. For example, if the goal is to improve the number of comments bloggers get from readers, we’d track how many comments visitors write each day before and after the change.
- Get to work. Designers design. Programmers program. Periodically someone checks the launch announcement to remind everyone of the goal. As more is learned about what’s possible, the announcement becomes more precise. Sometimes the feature pivots into something different and better.
- Launch. When the goal of the work has been met, the feature launches. It’s often smaller in scope than the initial idea, but that’s seen as a good thing. The code goes live, and there is much rejoicing.
- Learn. Data is captured instantly and discussed…by the folks who did the work. Bugs are found and fixed. For larger features, several rounds of revision are made to the design.
In the words of Scott Berkun,
“The fundamental mistake companies that talk about innovation make is keeping barriers to entry high. They make it hard to even try out ideas, blind to how much experimentation you need to sort the good ideas from the bad.”
The end announcement and web copy can now focus on honest and true good ideas, with clarity and simplicity, not messaging or spin.
On building trust for projects
Scott Berkun was recruited by the founder to be a team leader when Automattic moved from a flat hierarchy to 10 teams of five people. He was the only “outsider” recruited for this role, meaning he was at a bit of a disadvantage compared to the other nine Automattic-experienced team leads. But the advantage he had over the others was his past experience working in teams (for Microsoft) as well as his learned and intuitive understanding of how to build trust, including through regular communication processes.
If you think one of the primary remits of public relations is relating the inside out, and by extension the outside in, gaining the trust of a variety of employees necessitates demonstration that they are truly valued and being listened to for input regarding any final project and its outcomes.
Often it is administrative staff in support roles that are tasked with the record keeping of meetings, etc. What if a (senior) public relations staffer voluntarily agreed to do this role for applicable projects, not only to build trust, but to make the end communication more accurate and honest to all stakeholders, internally and externally?
“A trick is to take on the task of being the scribe. If you take notes, people have a chance to see how you think. If they find your recording of what happened clear and honest, you get a trust point. If the way you summarize complex things is concise but still accurate, you get another. Soon there’s enough trust to lead decisions and take bigger bets. Big upsides.”
If the scribe role is incorporated on a regular basis, the draft launch announcements and support pages should also become increasingly easier and instinctive to do, as a part of the lead role in the organizational narrative.
Some other project management terms learned from The Year Without Pants
Reading through the book occasionally a term or definition would be used of which I was unfamiliar or my understanding was imprecise, so I would make a note, with the consideration that it might come in handy for my own appreciation or direct application in public relations practice down the road. In this case, I was doing it from a project management point of view.
This is a practice I often employ when reading non-fiction books—creating an annotated notes version that will help to imprint the concepts into my longer-term memory and serve as a possible searchable resource down the road. Sometimes I will include my own notes within the copy, about an idea that sparks some original thinking or PR correlations on my part—this process helped me when writing my JPC article, in terms of the central thesis and organization of major points.
For the most part, the following wording of the definitions and examples come directly from author Scott Berkun.
From Eric Raymond’s book, The Cathedral and the Bazaar (which is about observations on making software) the central question is asked, “Is it better go invest time in making a big, masterful plan or instead to begin immediately and figure it out as you go?”
Cathedral-style thinking: Imagine the architect of a towering skyscraper or the director of a big film, you probably envision a singular brilliant tyrant who has detailed plans and a grand schedule on how everything will be done and unfold.
The bazaar: Imagine a young punk rock band jamming together. They start with something small, a few basic chords, but quickly revise it, and revise it again, each contributing, borrowing, experimenting, and collaborating as they wish.
Instead of grand central planning, a community of work forms around an idea and grows. Many famous open source projects, such as the Linux operating system, were developed using bazaar attitudes and this inspired Raymond’s book. The absence of a grand schedule removes the constant fear of falling behind that many projects create and replace it with small but frequent payoffs, leading to the belief that the company is making things better.
Product thinkers: People with visions for entire product concepts; these individuals with entrepreneurial instincts are found inside a company.
Broken window theory: By regularly fixing small things, you prevent bigger problems from starting.
Defensive management: The fear of big mistakes or falling behind schedule is what motivates most of the project management processes used around the world. The more experienced that managers are, the longer the list of bad things they’ve seen and are trying to avoid. This is what is called defensive management, because it’s designed to prevent a long list of bad things from happening.
Defensive management is blind to recognizing how obsessing about preventing bad things also prevents good things from happening or sometimes even prevents anything from happening at all.
Continuous deployment: The philosophy of endless small changes, allowing for Automattic to “ship” small modifications or innovations all of the time to its WordPress and WordPress.com blogger clients.
Daily build: Microsoft’s Internet Explorer team had an equivalent, where they released a version of the software every day, but the modifications or changes were available exclusively inside the company.
Cargo cult: Superficial mimicry. In anthropological terms…this is a reference to the misguided worship of abandoned airplane landing strips among tribes hoping for the goods that (earlier) airplanes had delivered to return.
Advice paradox: No matter how much advice you have, you must still decide intuitively what to use and what to avoid.
T-shaped skills: This type of person has one very deep skill set, and a wide range of moderate proficiencies.
Heisenberg uncertainty principle: As applied to distributed/remote work, people need both to know themselves well and also how to be “outgoing” (and communicative) online.
Creative abrasion: A theory of work that you need the right amount of friction for good work to happen—not too much and not too little—and that few managers get it right.
Refactoring: The word means you’re going to take the guts out of something one part at a time and rework it without disturbing the rest of the “body.”
Project trap: Postponing little things no one wants to do to until the end, when they cost more to do.
If what I’ve written here has piqued your interest but you have yet to decide whether you want to invest money and time into The Year Without Pants, I’d recommend you download the first chapter, watch the video “trailer” for the book and perhaps read some of the Amazon reviews. And of course check out my more-comprehensive JPC article when it publishes—I will update this blog post to include a link.
In the meantime, I welcome your commentary or questions about what I’ve written here.
* * *
Disclosure: In September I was offered a review copy of The Year Without Pants by a publicist for Jossey-Bass (A Wiley Brand). I had no prior relationship with this publicist, Scott Berkun or Automattic—above and beyond PR Conversations being a WordPress.com platform (registered to our Techster, Markus Pirchner). There was no stipulation for me to review the book in any form or platform. I have chosen to do so because I think the book has value, not only about project management, but from a public relations point of view.
Image: I took this photo the day my copy of the book arrived. Behind the book you can catch a glimpse of my treasured AP (i.e., “artist’s proof”) Luke Painter print, National 1. (How cool is it for an artist to be born with the surname of Painter?) Here’s a link to the twitpic photo I’ve used (a different one), where you see more of my print.