Writing has been a core element of my professional identity for approximately forever. As a former consultant and academic, this isn’t surprising. It’s a skillset that has been rewarded and reinforced.
I’ve written a host of deliverables over the years;
- Teaching cases
- Blog posts
- Magazine articles
- Book reviews
- Books
- Keynote speeches
- Lectures
- Dissertation
- Client Proposals
- Client Reports
- System Designs
- Procedure Manuals
- Training Manuals
- Training Courses
- Newspaper articles (High School Paper)
- Yearbook articles (High School and College)
I’ve edited and been edited.
More than enough evidence to be comfortable knowing that I write better than most. And, well read enough to know how many better writers exist.
What’s on my mind is a shift in perspective.
What flows from thinking of myself as a writer rather than a consultant or teacher or executive? If I place this collection of skills, practices, and experiences center stage, dress it in a costume (tweed jacker perhaps), and hang a sign around my neck that says “WRITER” where does that lead?
There’s no shortage of advice about the importance of choosing the right word. I’ve also been troubled that I haven’t been finishing work as easily or as often as I would like. What can I discern from the perspective of “writer” that isn’t evident from that of “writing”?
In my world, writing was tied to deliverables and deadlines. There’s a product to create and an expectation of when it must be done. Nothing earthshaking in that observation. In my consulting career, I’ve called in freelance writers to handle those tasks for me. Good ones deliver product at or before the deadline. The others don’t get hired a second time.
A good freelance writer needs to manage their work beyond the individual deliverable. Whatever skills and techniques they bring to bear on completing an individual assignment, they need a separate set of skills and techniques to manage their writing practice.
Knowing how to complete individual deliverables has little bearing on managing a portfolio of requested deliverables. It has less bearing on how to think about or manage a queue of deliverables.
It’s hard to solve a problem when you’re looking in the wrong place. Which appears to be what I have been doing. So much for the benefit of experience.
When I was writing to spec for others, they managed the process. I focused on their deliverable and their deadline. As a writer, writing for myself, I must take responsibility for both the deliverables I know how to create and the overall process.
Elements of that process can be found within the emerging practice of personal knowledge management (PKM). Being more disciplined and systematics about keeping the intellectual tanks full of my own and others’ ideas, capturing ideas as they occur to me, noticing connections between ideas. Simple tasks that gain power from consistent practice.
These need not be discrete activities. They can become components of a larger process or system. That larger system might be the responsibilities of a knowledge work job or career. For example, that of a writer. Responsibilities that belonged to someone else in a larger, organizational context need to be folded into the writer’s individual context. Mapping individual ideas to potential deliverables, choosing which potential deliverables to develop into works in progress, managing the queues of potential deliverables and WIP, polishing and sharing WIP as finished material are elements of this larger system. They are no longer discrete activities. They are now components of a system that needs to be designed. A design that includes the capacity to monitor and manage the system.
I’ve developed a troubling habit of blaming my issues on my underlying neurodiversity. That’s a contributing factor. But the bigger issue is that I haven’t put the system in place that makes management possible.
What comes to mind is an old observation of Alan Kay’s, “point of view is worth 80 IQ points.” There’s work to be done, but I believe I’m now looking at a promising framing of the task.