Guy Reams (00:00.962)
This is day 257, the Eating Pancakes Initiative, aka writing your own job description.
Guy Reams (00:12.174)
I've cataloged over the course of my career, some of the stupidest, most irritating things I've been asked to do by an employer. And high on that list, top 10 easily is this, write your own job description. I almost sent one back one time with a one-line response in the email. This job description is subject to change.
Seriously, who has ever had a job where what you're supposed to be doing doesn't change every five minutes? I've decided to look into this and apparently this is a real trend in today's professional landscape. Not only are job descriptions subject to change, but in many environments, your actual role will shift entirely every three to six months. This is the new normal. It's beyond the typical occupational lifecycle trends we've seen in the post-industrial economies.
We're heading into a future where so much is being automated, the tasks people need to work on assist with or validate will constantly shift. So why do job descriptions really change? Sure, there have always been reasons to update job descriptions. HR departments will give you a dozen of them. None of which I can remember. I'm sure it involves performance evaluations, salary bans and compensation benchmarks.
But let's be honest, the real reason job descriptions change is purely financial. Businesses are constantly adjusting compensation to reflect cost of living increases, wage pressure, and shrinking margins. Since labor is often the largest cost center, job descriptions become a tool to justify or re-justify pay rates based on skill set. Enter the pancake initiative. In my case,
My boss had been asked by HR to provide updated job descriptions for highly compensated employees. This was almost certainly due to what I call the Eating Pancake Initiative. If you're unfamiliar with the term, let me explain. One of the age-old cost-saving strategies used by consulting firms is to attack the layers of middle management. Over time, every company trends towards complexity. You hire a manager,
Guy Reams (02:32.866)
That manager hires other managers and so forth and so on. To control this growth, companies often create strict policies. For instance, a sales manager may be required to supervise no more than 20 and no fewer than eight salespeople. That's a policy meant to control middle management costs. The more complex the business, the lower the manager to employee ratio will likely be.
but there's always pressure to consolidate. That's where the pancakes come in. Eating pancakes is my affectionate term for flattening the organization, finding overlap and redundancy so that you can collapse layers and reduce headcount. When a high-priced consultant comes in, they always start with cost efficiencies. The first meeting often starts with, well, we have some good news.
We found opportunities for significant savings with just a few simple organizational changes. And I always respond, great, I love eating pancakes. They always look at me cross-eyed until they show me their first slide. And sure enough, it looks like a stack of pancakes. Top level management, the workforce below, and a mushy middle, it's about to get eaten alive. So about that job description.
So when my boss asked me to write my job description, I knew exactly what was happening. I wasn't in the pancake meeting, but I was clearly the one stuck in the middle of the stack. I was now being asked to justify my existence. What my boss was really saying was, I've lost control of my org chart. We're not growing fast enough. And a consult firm has been brought in to optimize things, starting with high paid middle managers like you.
And while that's not the point of this blog, I will give one piece of advice. If you're asked to write your own job description, know this. You're being asked to write a document that helps prove that there is a redundancy. Don't simply write that you do, right? Don't simply write down what you do. Instead, write why you are unique and why you are pivotal to the team or division success. Write it so clearly and so compellingly.
Guy Reams (04:56.344)
The consultant has to invent a brand new category just for you. Sounds like a perfect job for an AI tool, but I digress. Writing a job description for yourself. Let's return to the original thought. What if the request to write a job description came from you?
That was my thought today. What is my actual job? What is the role of Guy in the Guy Rheem circus? What purpose do I serve? What are my responsibilities? What are the working conditions, expectations? And here's the kicker. How much should I be paid for this role? Let me tell you something. Being me, working for me is brutal. I'm a very annoying boss.
demanding, needy, borderline psychotic. I micromanage myself. I use guilt, fear, and intimidation all the time. I expect far more of myself than I am capable of delivering. And when I fall short, I pile on even more. I change my mind constantly. I'm unclear, scattered, and unreasonable. And the benefits? No breaks, no PTO, no recognition.
I wear every hat, CEO, CFO, CTO, CMO, CRO, all of the Cs. If I were interviewing for the job of me, I'd say, hell no. You'll have to pay me 10 extra offer and throw in more. You'll have to throw in a lot more than just a few of those unvested options.
The exercise. After that little tantrum, I actually started writing down what I do. The list was long. Every time I thought I was done, I'd remember something else.
Guy Reams (06:45.866)
One observation, I'm pretty good at accounts payable, but accounts receivable, not so much. That's a joke, by the way, in case you missed it. Payable is what you owe, receivable is what you earn. Joking aside, this exercise was strangely therapeutic. It helped me understand why I feel so stressed sometimes. I'm overworked, underpaid, and unfortunately, I don't have the guts to show this job description to my wife. So let's just keep that between us friends.
How much are you actually worth anyway? This brings us to the question of compensation. When you work for someone else, you're trading time for money. So how much is your time actually worth? How much does your employer think it's worth? And more importantly, how much do you think it's worth? I recently talked with one of my kids who got a part-time job. She was thrilled to receive a little overtime.
an extra $250 in her paycheck. Of course, then there's taxes, but we'll save that subject for another day. Then I told her that a professional with the right experience can make that much or more in just one hour. She wanted that too, but the follow-up conversation was sobering.
Nobody pays 250 an hour to clean tables at a restaurant. Enter the need for qualification, experience, or building something people are willing to pay real money for. Another example, a salesperson once proudly showed me a massive commission check. After all the high fives, I asked how long they'd worked on that deal. The answer, months, months and months, nonstop. When we did the math, they'd made less than minimum wage per hour.
Deflating, yes, but also a highly valuable reality check. So is there time for a self-audit? Here's my ultimate point here. Every so often it's worth writing your own job description, not just at work, but in your life. Do some management consulting on yourself. Take a hard look at what you're doing. Are you spread too thin? Have you added so much complexity to your life that you've become your own worst boss?
Guy Reams (09:05.639)
Maybe it's time to eat some pancakes and flatten your own organization. Not everything you've been doing still has value. Maybe you're just stuck in old habits. Maybe you're living beyond your time budget. Maybe you're trading your most valuable hours for the wrong kind of return. So take a minute, write your own job description. Be honest, be bold. Then figure out what you're worth, because you might be worth far more than what you're getting.