What am I? I feel my blog has been asking me this question since I started.
“Am I a place for the author to tell his story about making his life Boring?”
“Am I a place for the author to hash out his thoughts on a life philosophy that he thinks is worth spreading but still in its infancy?”
“Am I a place to discuss productivity hacks, which became the obvious evolution of the blog?”
“Am I an accountability partner to make sure that the author keeps pushing on his passion projects?”
“Am I just a waste of time to keep the author feeling productive and important while not providing any real value?”
“Or maybe I’m all of these things, while also being none of them?”
I feel like most of my posts was me telling my story. But then I wrote Project Organization where I detailed how I plan on tackling some of my ambitions. I enjoyed writing it; it felt like I was providing value. I’m a pretty private person and don’t like talking about my personal life. I'm so secret that when I had my youngest kid, I didn’t tell anyone at work for a good six months. I told my boss and HR so that I could get paternity leave. But my coworkers and even my direct reports thought I was just on vacation. So sharing my story is uncomfortable and as much as I know there can be value in it, I have a hard time convincing myself others will find value in it. However, figuring out and sharing a way to effectively setup Project Organization in your personal life; that’s different.
I talked to my wife last night about how I wasn’t vibing with the blog. I was thinking about how it’s not possible for me to come up with something value-adding every week. I’ve had enough thoughts to keep my posts pre-written to sustain a weekly release schedule, but I never intended to keep that frequency. So if I can only think of a value-adding item once a month or even less, that’s fine. But I have to be honest with myself. If I am jumping on the blog once a month or less, I’ll forget about it and move onto something else. I had a problem on my hands.
Tonight she pitched some ideas to me, we brainstormed a bit, and I hit a revelation. I’ve mentioned before that I’m an engineering manager in charge of four teams and almost two dozen engineers. Every year both the number of projects I manage and the total headcount has too. In my opinion, this is because I’m very skilled in creating a system. Instead of engineering software, I feel like I’ve engineered a culture and environment for my teams. I have daily and weekly checklists that I go through to keep the team’s train on the tracks. I have what I call my Team Control Book detailing full transparency on what I do so that the teams stay informed of what I’m thinking, what I’m focusing on, and what I expect of them. In this Team Control Book, I also have our core processes and even some culture items. It’s only about a half dozen documents that I tweak and trim to keep it current, relevant, and as concise as possible.
I don’t have a similar system in place for my personal life. I have various documents here and tools there, but since I don’t have a team to work with, I’ve never formalized it. Why create a Personal Control Book for me, myself, and I? That’s where I went wrong.
Since starting to think about Boredom is my Goal as a philosophy, I’ve been able to focus on my Big Rocks more easily. But not until the last post did I start to think about my projects as a system. So that’s what this blog has become.
This blog is my team. Even if no one reads it, that’s irrelevant, because the results speak for itself. So it doesn’t matter if anyone reads the blog. The only thing that matters is results in my projects.
I think I’m going to create three main purposes to this blog now. By the time this writing goes public in a few weeks, we’ll see if I follow through.
The first purpose is to tell my story. Since this makes me uncomfortable, I need to keep doing this. It’ll help me grow. I'll continue doing my regular Thursday release schedule. On this schedule, I can talk about what I’m doing, why I’m doing it, what I’m failing, and where I’m going. It’s all the “feels.”
The second purpose is to start building out my Personal Control Book. This control book will mirror the Team Control Book I have at work. It’ll be static pages on the site where I detail my processes. The Thursday release schedule can talk about how and why I came up with my Project Organization, but the static Personal Control Book page will remove all the personal details and document how it works.
The third and last purpose will be to provide accountability for myself. At work, I do a Weekly Update so that everyone on the team knows what’s what's happening on the team, in the division, and at the company. It’s become the primary way for a distributed team to keep connected to everyone else. So to mirror this, I’m going to start doing a Weekly Update post on Sunday nights to recap accomplishments during the previous week.
All the pieces are coming together. My blog’s identity is starting to come into focus.
(Written 2019.03.28)
“Am I a place for the author to tell his story about making his life Boring?”
“Am I a place for the author to hash out his thoughts on a life philosophy that he thinks is worth spreading but still in its infancy?”
“Am I a place to discuss productivity hacks, which became the obvious evolution of the blog?”
“Am I an accountability partner to make sure that the author keeps pushing on his passion projects?”
“Am I just a waste of time to keep the author feeling productive and important while not providing any real value?”
“Or maybe I’m all of these things, while also being none of them?”
I feel like most of my posts was me telling my story. But then I wrote Project Organization where I detailed how I plan on tackling some of my ambitions. I enjoyed writing it; it felt like I was providing value. I’m a pretty private person and don’t like talking about my personal life. I'm so secret that when I had my youngest kid, I didn’t tell anyone at work for a good six months. I told my boss and HR so that I could get paternity leave. But my coworkers and even my direct reports thought I was just on vacation. So sharing my story is uncomfortable and as much as I know there can be value in it, I have a hard time convincing myself others will find value in it. However, figuring out and sharing a way to effectively setup Project Organization in your personal life; that’s different.
I talked to my wife last night about how I wasn’t vibing with the blog. I was thinking about how it’s not possible for me to come up with something value-adding every week. I’ve had enough thoughts to keep my posts pre-written to sustain a weekly release schedule, but I never intended to keep that frequency. So if I can only think of a value-adding item once a month or even less, that’s fine. But I have to be honest with myself. If I am jumping on the blog once a month or less, I’ll forget about it and move onto something else. I had a problem on my hands.
Tonight she pitched some ideas to me, we brainstormed a bit, and I hit a revelation. I’ve mentioned before that I’m an engineering manager in charge of four teams and almost two dozen engineers. Every year both the number of projects I manage and the total headcount has too. In my opinion, this is because I’m very skilled in creating a system. Instead of engineering software, I feel like I’ve engineered a culture and environment for my teams. I have daily and weekly checklists that I go through to keep the team’s train on the tracks. I have what I call my Team Control Book detailing full transparency on what I do so that the teams stay informed of what I’m thinking, what I’m focusing on, and what I expect of them. In this Team Control Book, I also have our core processes and even some culture items. It’s only about a half dozen documents that I tweak and trim to keep it current, relevant, and as concise as possible.
I don’t have a similar system in place for my personal life. I have various documents here and tools there, but since I don’t have a team to work with, I’ve never formalized it. Why create a Personal Control Book for me, myself, and I? That’s where I went wrong.
Since starting to think about Boredom is my Goal as a philosophy, I’ve been able to focus on my Big Rocks more easily. But not until the last post did I start to think about my projects as a system. So that’s what this blog has become.
This blog is my team. Even if no one reads it, that’s irrelevant, because the results speak for itself. So it doesn’t matter if anyone reads the blog. The only thing that matters is results in my projects.
I think I’m going to create three main purposes to this blog now. By the time this writing goes public in a few weeks, we’ll see if I follow through.
The first purpose is to tell my story. Since this makes me uncomfortable, I need to keep doing this. It’ll help me grow. I'll continue doing my regular Thursday release schedule. On this schedule, I can talk about what I’m doing, why I’m doing it, what I’m failing, and where I’m going. It’s all the “feels.”
The second purpose is to start building out my Personal Control Book. This control book will mirror the Team Control Book I have at work. It’ll be static pages on the site where I detail my processes. The Thursday release schedule can talk about how and why I came up with my Project Organization, but the static Personal Control Book page will remove all the personal details and document how it works.
The third and last purpose will be to provide accountability for myself. At work, I do a Weekly Update so that everyone on the team knows what’s what's happening on the team, in the division, and at the company. It’s become the primary way for a distributed team to keep connected to everyone else. So to mirror this, I’m going to start doing a Weekly Update post on Sunday nights to recap accomplishments during the previous week.
All the pieces are coming together. My blog’s identity is starting to come into focus.
(Written 2019.03.28)