2024 Weeknote 24 : Reboot. Restart. Repeat.

June 10 – 16

These are my “weeknotes” to capture events, thoughts, and other items from the past week, mostly focused on work, but with some personal stuff thrown in.


What a week. It was 5 days in the office with lots of meetings to keep lots of things moving forward, including whole teams, big projects, and so on. Very little time for personal stuff this week.

Rebooting a culture

In May 2024 I took on a new team, in parallel to the GX Foundry group. It’s a team that pre-dates my arrival in my role and a team that has struggled to consistently get great work done. There are a lot of reasons for this, all of which have nothing to do with the people on the team and everything to do with past poor management (that’s now gone). It’s now my job to lead the team through a “reboot” of both culture and processes. And culture comes first.

On Friday I presented my own perspectives on the past and asked the team to help me think about how we’re going to build the future—which will be radically different from that past. Everything is up for discussion, debate, and re-consideration. This is a team that’s had 133% turnover in the last 3 years. They’ve had 5 major leadership changes in the last 15 months (including reporting up through me last month). Any team that goes through all that is going to struggle in one way or another. And those are just 2 of the stats holding them back. We’ve got work to do.

To kickstart the reboot, I got help from the amazing Sarah, who facilitated an “expectations exercise” that began to pull from the team what we’re all going to expect from one another, in terms of behaviors and attitudes. It was my first time through the exercise, expertly facilitated by Sarah. (And we’re gonna do it again with another team next week.)

The result is a (draft) collection of expectations that (1) Leaders have of the Team, (2) the Team has of Leaders, and (3) we all have of one another in general. You can see the draft above (click for a larger image).

This is all subject to future revision, of course, as the team matures and we figure out what works, what doesn’t, and what’s missing. But this feels like a great start. Now we just have to live up to these expectations, values, and beliefs. I’m excited to see where we take this!

You can be undermined with or without intent

This week revealed some of our efforts were being undermined by forces beyond our organization, out in the broader government environment.

When there’s a person behind the undermining, making it happen, it’s easy to get mad at that person. But when there’s just cross-cutting priorities that conflict—without anyone’s intention—you can’t get mad, but it’s still frustrating.

In the first case this week we learned a former employee in one of our partner agencies was actively undermining our major new countywide project. We’re trying to switch public-facing websites and digital services from government-centric content to citizen-centric and service-focused. A laudable goal we thought everyone would support. But this person was mad it wasn’t happening in his department—despite (a) never having proposed anything even remotely similar, and (b) sitting in an agency that is not a neutral player in our broader government, and therefore cannot effectively host this kind of project.

It wasn’t really a surprise this person had done this—he was a known irritant on past projects as well. What was surprising was the extent of his success in deceiving powerful people in the upper echelons of our county. (Proximity to power is a power of its own.) He was communicating directly with certain leaders, and we were communicating indirectly. We assumed positive intent. He did not.

At least he’s gone now. Starting next week we must establish direct communication lines with the affected leaders to both give them the facts and ask for their support. Then we’ll have to keep those communication lines open.

Photo by Gratisography on Pexels.com

In the other example, we have apparently bumped up against the aspirations of someone we’ve been working with for a while. But their personal aspirations and our team aspirations appear to conflict in ways we didn’t anticipate. It’s created some friction and we have to figure out a way for everyone to win. This is a problem I would much rather solve because there are usually ways for everyone to “win” either together or in parallel. The conflict still hurts, but it feels like we can make something good out of this.

Naturally, I’m being coy by not naming names or describing the situation clearly, as I don’t want to hurt anyone’s feelings or create more conflict. My point? I’ve had to acknowledge some conflicts in the world are created by intentional negative action, but others are emergent properties of people working in close proximity. It’s important to know the difference and deal with them differently.

Another realization? The cacophony of modern work makes fully communicating intentions, goals, and actions really, really hard. Even if everyone wants to align it’s hard to establish and sustain the alignment. When you’re “done” communicating, you’re not.

Take me out to the ballgame

This was fun. 😎 Lucinda put together an outing to the Columbus Clippers this week, and several folks from the office took part. I did a lot of these games last year (and need to do more this year) because Huntington Park is an awesome venue and a baseball game is a great place for some casual socializing with workmates. Thanks Lucinda! And thanks also to Brian, Michael, Eric, Nora, and Tony for coming out to make it fun.

Group selfie photo courtesy of Eric Nutt

Miscellanea

  • The Recognition Program I started earlier this year (with mission patches in the form of stickers) was paused a little while some other stuff got done, but it’s coming back. We’ll have stickers galore coming our way soon, with distribution to folks across the organization in July. Really looking forward to that!
  • We’re hiring for a Project Manager role, and that always keeps me super-busy with calls, interviews, and discussions as we hash out exactly what our priorities are with each hire. I try to use every hiring event as a chance to diversify skill sets across the target team. It’s hard to do that with a 30-minute call and maybe 2-3 hours of interview time.
  • We were making some high-level design decisions this week about the next wave of website overhaul work, slated to go live in early 2025. There’s definitely some disappointment out there that we’re building a kinda “generic” site. But when your focus is public service, “generic” is a plus — you don’t want people to have to learn how to use your unique cutting-edge website. We actually want them to find our services, not be dazzled by graphic design. We gotta remember our True North here.

Internet funnies

A roundup of stuff that made me chuckle this week, mostly from Bluesky.



Yes. Yes, I would. It’s called vaccination, Mara.


2024 Weeknote 21 : Reloading…

May 20-26

These are my “weeknotes” to capture events, thoughts, and other items from the past week, mostly focused on work.

Photo by Karolina Grabowska on Pexels.com

I moved. Digitally.

I grew tired of the sprawling digital estate I’ve been maintaining personally, so I decided to collapse several digital properties into the one you see here. In fact, this is the first “native” post on the new site and domain name. All other content on this site was migrated from other platforms. This new digitalpolity.com site brings together:

  • My Medium presence, which I used for mixed essays. I really like Medium in terms of features, but I didn’t like how so much of Medium’s content is behind a paywall and they’re not innovating the platform very much.
  • A Substack site I created just for publishing . While I am aware of the “Substack supports hate speech” controversy, that’s not been my main concern. I’m more concerned, about Substack’s future simply because I want to publish for free, but they are moving fast to monetize and free users might get kicked to the curb. WordPress has been a more reliable and responsible player for a long, long time, so I trust Automattic, uh… automatically.
  • A WordPress-based photo blogging site that I like, but I just don’t want to maintain separate sites, so I’m integrating that one into this one.

The GX Foundry site will remain wholly separate and it will stay on Substack. That’s a more formal shared-authorship site and the limited features of Substack are a plus, not a minus. Maybe one day we’ll move to Ghost or even here to WordPress. But for now, Substack is fine. I mean, Jennifer Pahlka is there, so that’s something.

Finally… why WordPress? Several reasons.

  • I’ve used WordPress off and on for a couple decades now, so it’s familiar
  • They now charge real money for their features, which is a good sign — it tells me I’m their customer, not their product
  • There are tons of integrations, in case I need something that’s not there
  • They caught up with the newsletter trend, so it’s much easier to offer that option now
  • They play nice with the Fediverse

See you at #CfASummit

Had fun making this graphic to share on LinkedIn. We really are excited to attend the Code for America Summit for the first time. Wish it could be in DC, since that’s a lot closer, but the Bay Area should be fun, too.

Our team:

Local conferences need an upgrade

This past week I attended an “IT Leadership” conference and it was… meh. As I’ve told my boss and some colleagues, I am a bit of a conference snob, having worked in public media in the past. Go figure: people that run radio and TV stations know how to put on a show.

These days local conferences aren’t organized by professionals in your field, they are run as money-making operations by publications of one kind or another. And while they may have good intentions, it leads to less-than-optimal results because:

  1. local professionals are busy and don’t have the time or energy (or sometimes the expertise) to prep national-quality presentations, and
  2. the publications playing host are more focused on collecting and selling contact lists to sales folks in the industry.

I actually have some ideas for improving local conferences, and even some ideas for starting one from the grassroots level. Shoot, in early 2023 I created my own day-long in-house conference at and it went pretty well. The key, as always, is focusing on the needs of the audience.

So until I have some meaningful direct input over the local events, I won’t be attending any more. It’s too much effort for too little payback. I’ll stick to national conferences or at least major regionals. And I’ll study the agendas closely before committing.

Miscellanea

Not much more to report this week, as there was an all-day meeting, an all-day conference, a day off on Friday (to make up for losing Memorial Day to travel for ), and the rest of the time was just keeping up with stuff. That said, I did complete my initial “listening tour” with the Delivery Services team, getting their thoughts on what beetn going well, what’s not been going well, and ideas for how we can improve.

Internet funnies

And now a random roundup of stuff that made me chuckle, most often from Bluesky.








To hire in government IT, cover the basics, but promote the meaning of your mission

I originally published this post on Medium. I copied it here in May 2024 to keep it alongside my other content.

Back in February I wrote about talent attraction and retention in government. It’s a growing hot topic in circles as the Boomers retire and lots of younger professionals (Gens X, Y, and Z) have pursued more popular and often more lucrative jobs.But it’s not hard to figure out how to make GovTech jobs attractive.

Photo by Nick Fewings on Unsplash

Longtime tech and management pundit Bob Lewis covered this (indirectly) in a recent column titled Human performance — the essence of IT effectiveness. Bob’s short list to cover:

  • Leadership
  • Staffing and skills management
  • Compensation and rewards
  • Organizational structure
  • Team dynamics
  • Culture

Meanwhile, for anyone hiring in GovTech, all this boils down to doing 2 things well.

  • First, make your jobs worthy of professional attention — ensure your culture, compensation, titles, and growth options are covered well enough, like any employer. Get all the basics right, and you won’t have to fully compete on compensation. (Indeed, you probably shouldn’t even try.)
  • But second, lean hard into promoting your public service mission and the positive impacts your team brings to your local or regional communities.

People want money, sure. But they also want purpose and meaning (not to mention autonomy and mastery). Take the money issue off the table (just barely) and focus instead on your “why.” You’ll attract candidates better suited to building the culture you need, they’ll stay longer, and the truly inspired ones will help you innovate.

If employees do okay in pay and benefits, but get a chance to make a meaningful difference, you’d be surprised how many folks would be delighted to join your GovTech team.

SMART goals? Maybe not so smart after all.

Photo by Glenn Carstens-Peters on Unsplash
I originally published this post on Medium. I copied it here in May 2024 to keep it alongside my other content.

Do you resist using “SMART” goals like I do?

The concept seems logical and useful, but I can’t say I’ve seen them work. SMART goal-setting is typically connected with quarterly or annual “performance reviews.” Or worse, it’s attached to disciplinary procedures — achieve these goals or you’re outta here. I’ve never witnessed someone setup a series of SMART goals and knock them down like bowling pins.

So… SMART goals? I’m a solid “meh.” But I couldn’t articulate why.

Then I stumbled across this article and… I feel seen.

How to Achieve Big, Hairy, Audacious Goals: Don’t Be SMART
https://www.psychologytoday.com/us/blog/recover-girl/202308/how-to-achieve-big-hairy-audacious-goals-dont-be-smart-0

So if SMART seems dumb to you, check out GAP, and push yourself, employees, and colleagues to go after their BHAGs instead.

Attracting and retaining tech talent in local #GovTech

I originally published this post on Medium. I copied it here in May 2024 to keep it alongside my other content.

Next week The Atlas is hosting a roundtable discussion focused on workforce retention and hiring issues facing local and state governments across the country. I’ll be participating, but with only 90 minutes, a broad topic, and lots of people with opinions I’d like to hear, I figured it might be easier to share my answers to their thought-provoking questions here rather than taking up time in the meeting.

With permission from organizer Gabby Manocchio, I’m sharing the discussion questions, with my own answers, based solely on my experience to date, combined with prior experience in nonprofits and for-profits.

Where I’m coming from

  • I’ve worked in for-profits and nonprofits in the small/medium business (SMB) space for over 25 years, but local government has only been the last 3.5 years of that work, so my views may be skewed by my limited government exposure.
  • I work in County government in central Ohio, with a metro population of about 2.2 million today, trending to 3 million by 2050. So my thoughts may not scale up or scale down to all other environments. For a sense of scale, I lead a team of about 60 infrastructure and software folks.
  • I work in IT leadership, so my perspective is geared toward tech staffing rather than general government staffing.
  • I believe the best-tasting steaks come from sacred cows. 🙂 Put another way, I take “that’s the way we’ve always done it” as fightin’ words — usually a sign that things are ripe for change. I’m also allergic to the notions that “government is different” and “we can’t do that here.”
  • My opinions are my own; I don’t speak for my employer here on Medium.

Government workforce questions from The Atlas

Below are the Q’s posed by The Atlas and the A’s I have to offer ahead of the roundtable discussion. If my commentary isn’t clear, you have an alternative view, or a question, please share your thoughts in the comments.

[1] What are your biggest concerns related to your IT workforce?

We’ve been pretty good at attracting and retaining talent since 2019, but we definitely have some concerns, mostly centered on ensuring we’re following a continuous improvement path. For example:

  • We need to consistently foster a “growth mindset” culture from recruiting through employment — but this is very hard to teach and sustain in the face of Too Much Work and the “government” culture surrounding us. We know that people who grow professionally, while contributing to a larger mission, provide the most creative, most valuable results in a world of shifting priorities. And without a growth mindset, employees can stagnate and disconnect. So this is a big concern.
  • We desperately need better work management and coordination tools, especially in an age of remote / hybrid work. We also need better work management methodologies to address visibility, agility, and product-focus needs. Models like Kanban, Lean, Agile, and Product Ownership have helped, but they still feel incomplete or poorly implemented in software tools. We’re hoping tools get better now that hybrid work is dominant in the industry.
  • Finally, we’ve got to get better at building, sustaining, and evolving our culture to get the best out of hybrid working models particularly. We’re improving, but wow… this still feels like the “wild west” and we’re stumbling our way through it. I’m proud of what we’ve done, but I’m always worried we’re missing something.

[2] Have you experienced changing employee expectations since the onset of the pandemic?

  • Employees immediately expected remote work, and we did it, like almost everyone else, in 2020. We also worked hard to extend remote work technologies to our customers very, very quickly. In 2021 we codified a “hybrid” working model for our staff (which I address in the final question below). Remote-first hybrid work is now a core expectation of staff, and it’s our baseline model.
  • George Floyd’s murder in the midst of COVID-19’s ascendance launched a series of DEI efforts across all layers of our local government. However, there’s a broad spectrum of employee expectations about DEI ranging from “we need a transformative DEI program yesterday” to some staff dreading those three little letters as a veiled threat to anyone that isn’t an “other” of some kind. So DEI expectations are all over the map and are actually generating some amount of cultural friction, even amongst an unusually diverse / progressive IT practice like ours. Personally, I’m starting to think focusing lots of energy on identifying our differences is damaging our ability to see our commonalities as human beings and our shared public service mission.
Photo by Tim Mossholder on Unsplash

[3] What strategies have you tried or found successful in attracting & retaining top IT talent?

I’ll address these in 3 sections: things we do to attract talent, things we do to retain talent, and more stuff we’d like to do but haven’t been able to get done yet.

ATTRACTING TALENT

  • We completely rebuilt our job descriptions in 2019–2020, focusing on both tech skills and soft skills, with built-in growth paths (1–2–3) for most roles. This has allowed us to be specific about what/who we’re seeking, and to stratify our pay bands clearly.
  • When posting jobs, we save the detailed job description for later conversations and instead use a marketing-style slide deck to promote the company, position, and the interesting challenges the job offers to prospective candidates. We are “selling” ourselves more than ever before.
  • We specifically talk about how working here has a public service mission component, in the hopes of attracting talent compatible with our goals. That talent is more likely to stay longer and appreciate the intangible benefits of having a built-in Purpose.
  • We’ve sped up our hiring cycles, despite having some structural barriers to hiring quickly. We can go from posting a job to screening phone calls in as little as 24 hours, and interviews can start in as little as a week. If the timing is right, we can go from job posting to formal hiring in as little as 2–3 weeks, which can be up to 4X faster than prior efforts. Candidates appreciate this, and it gives them a palpable sense of how we will respect them and treat them if they join the team.
  • Hiring processes — including interviews — now include peer staff and a cross-disciplinary mix of managers. Interview panels can be a little daunting for candidates, but our approach captures more diverse perspectives and allows candidates insight into who we are and how we operate — openly and collaboratively. It also trains our team on how to run interviews and how to better perform in their own future job interviews.
  • Most positions we hire are remote-first hybrid roles, which many candidates now expect as table stakes.
  • Since we are now remote-first for most roles, we’ve been able to extend our geographical reach out to roughly 1 hour’s drive from our office. This gives us access to more candidates and allows us to hire staff from areas with lower costs of living, so we’re a premium-pay employer compared to small-town employers.
  • We aren’t yet posting jobs via paid LinkedIn postings, but we do have the paid LinkedIn Recruiter service to scout for candidates and build future talent pools. We also post socially on LinkedIn and ask employees to help us spread the word.
  • We now consistently post to Indeed for all roles. We’re only doing free postings, but that’s way better than what we did in the past, where all we did was post to NeoGov — which candidates never see. It’s crucial to meet candidates where they are.
  • All job postings include pay ranges. And we updated and expanded pay ranges last year to stay competitive.
  • Our pay is not market-leading, but we are fast-followers and do quite well in that department. Where we’ve got all our competitors beat, handily, are in healthcare and retirement benefits, which are nothing short of killer. Younger candidates don’t care as much about that, but mid-career professionals “get” the value immediately.
  • We tout the fact we’re growing (doubling in the last 3 years), which creates growth opportunities.
  • Finally, now that we’ve got a track record of quality hiring and a great culture, we’re getting excellent referrals to excellent candidates. Indeed, we’ve been known to poach multiple people from local companies. (Sorry, not sorry!)
  • Oh… one more benefit: government job stability. Candidates are attracted to that. But it’s a double-edged sword. Because if job stability is a candidate’s primary goal, they probably won’t be a great fit. We want people that take risks and grow — stable employment should only be a side-benefit.

RETAINING TALENT

  • To sustain culture despite the remote-first hybrid work model, we require each team to come into the office with their peers on the same day each week so they get face time, can get lunch together, attend meetings in person, and keep those human connections fresh.
  • We keep our IT gear (laptops, etc.) relatively current. Because IT people know the difference!
  • Our part of County government launched a 6-week paid leave benefit in late 2019. That’s had a huge impact on the perception of our culture.
  • In addition to remote/hybrid work, we also support flex schedules (within limits). This accommodates everyone minor life events that pop up year-round.
  • In cases where staff are called upon to put in extra hours for system failures or major deployments, and flex time doesn’t fit, we can provide “comp time” to be used as PTO in the future.
  • As hybrid work took off, we invested in Microsoft Teams Rooms gear to smoothly unite in-office and remote workers during live meetings.
  • We have a healthy training budget covering high-cost IT classes, certifications, and more. Everyone can get 1–2 “expensive” training classes per year. That’s pretty rare these days.
  • Whenever possible, we promote from within — including across teams — as staff build skills and demonstrate their growing value.
  • People in leadership roles at all levels are pushed to think carefully about our organizational and team cultures, and build sensitive but effective approaches to work management and people management.
  • Part of building a positive culture that retains top talent means asking people that don’t fit the culture to leave. Employees know when someone isn’t getting the job done or is a drag on the culture. Managers must work to fix those problems by coaching up or coaching out. Every time we repel bad-fit talent, we make it easer for good-fit talent to stay and grow with us.

MORE WE COULD DO

Despite all the good stuff we’re doing today, we know we can do more. Here are some additional items I’d love to add to our repertoire:

  • Our offices are dumpy, run-down, generic government spaces — they are uninviting at best. Tech people expect more. Additionally, our offices are setup for 100%-in-office work, not hybrid-work “hoteling.” We need to blow out the walls, redo the lighting and furnishing and create an attractive, professional coworking facility with a mix of solo and collaborative workspaces.
  • We need to figure out an equitable model to support employees building out appropriate home offices, including monitors, laptop docks, better videoconferencing gear, and so forth. So far we’ve offered no support beyond laptops.
  • We’ve never compensated for home Internet, mobile phone costs, or being scheduled for on-call duty. While not a top priority, it feels like these remain minor irritants we could address.
  • We need a organization name change and a new logo to accurately reflect who we are today, not who we were in the 1990s. I’ve done some work on that with one team, but we need to do more.
  • As fast as our hiring is today (compared to classic government), it’s still not fast or flexible enough.
  • Letting people go remains far too difficult, and we’re not officially permitted to grant employees we’re asking to leave a “soft landing” via reasonable severance packages. This needs work.

BONUS: Check out the recent HBR article Rethink Your Employee Value Proposition for more ideas for attraction and retention. It specifically addresses the vital idea that it’s not just about material compensation.

[4] How are these programs funded? Are your current approaches sustainable?

  • So far our County leadership has fully funded our operations and expansion in recent years, so it appears to be sustainable — so long as we continue to explain how we’re using these resources to provide tangible and intangible benefits worthy of the cost. Both pay and benefits are covered and in our growing region that should remain true for at least the next couple decades.
  • In terms of paying for training, we have a history of paying for lots of it, and we’ve simply maintained that annual expense. I’m not really sure how that got started, but we’re thankful it’s here.
  • We often tie staff expansions to specific efforts that are sometimes “pet projects” for elected officials and their appointees — the people with substantial sway over funding. Thankfully the projects are all legitimate (seriously… no pork barreling here), so we find it easy to prioritize that work and ask for funding and headcount.
  • We often ask for forgiveness instead of permission when it comes to spending on pay. That’s wearing thin as the years go on, but every year we’re showing value for money, so it’s been okay so far.
  • All our attraction / retention efforts are sustainable as long as we are fixing mistakes of the past, delivering results people care about, and outperforming peer government agencies.
Photo by The Climate Reality Project on Unsplash

[5] Are you investing in upskilling or apprenticeship programs to build IT capacity?

  • We don’t do apprenticeships. Those tend to be drags on productivity, and we already have employees in-house that are growing, that we can support, so we avoid interns and the like.
  • Our training budget is substantial, with a focus on relevant skills development and certification (to prove the training stuck).
  • We invest in internal promotion whenever possible, upskilling in-place, so to speak.
  • In 2023 I’m trying a new thing: a one-day, in-person, on-site custom “conference” aimed at promoting individual and team professional growth. We’re bringing in guest speakers, work style assessments, self-marketing training, and custom growth-mindset messaging to help grow our staff prospects over time.

[6] Does your government think about “employee satisfaction” or “employee experience”?

  • We do employee surveys inside our own agency once or twice a year and pay more attention to the results than a lot of staff suspect.
  • I just started a “GX” (Government Experience) practice in late 2022; it’s nascent and we’re learning, but our first major effort is to completely overhaul how the County presents itself to the public on the web, with a basis in government experience (user-centric) principles. So far this is focused on constituent experience, but many of our software products serve employees, too, and a focus on experience in one area should apply to all areas.
  • Our particular County government is fractured over non-aligned electeds, boards, and budgets, so we’re really the only ones thinking about GX in a unified / uniting way, but we are trying to tell that story to get supporters and adherents.

[7] Do you think retention strategies used in the private sector could be adopted to the public sector?

  • Sure, but what is the private sector doing that we’re not?
  • We have one major barrier in retention. Any retention benefits we offer cannot look like we’re providing “gifts” to employees. For example, we can’t provide performance bonuses to staff. Elected officials are even unwilling to provide basic coffee service to employees because of the optics. Put bluntly, there is palpable fear of anything that could be construed as “fat cat government hacks stealing from taxpayers,” even if the benefits retain staff, improve efficiency, and boost public services.
Photo by Christina @ wocintechchat.com on Unsplash

[8] What kinds of technology are/should you be using to facilitate this workforce transition and meet new expectations?

  • Hybrid-compatible conference rooms are a must to support in/out team meetings. Teams Rooms / Zoom Rooms.
  • Digital collaboration tools like Teams, Slack, M365 offerings, third-party stuff like Miro, Mural, Trello, and more to enable work management and document sharing are crucial.

[9] What is the dominant type of workforce model at your organization today? What will it be in the future?

  • Today most staff work under a remote-first hybrid model where they are expected to spend 1 day per week working in our offices, and other days can be remote. However, more in-office time may be needed to facilitate high-fidelity collaboration.
  • Lately our leadership team has grown increasingly concerned around the visibility and coordination of work efforts, and we’re concerned 1 day of in-office may not be enough. We’re not ready to mandate more time in-office, and we have to consider the needs of our more far-flung employees, but it feels like more face-time would be beneficial. We’ll be discussing that with our teams this year.

Photo by Markus Spiske on Unsplash

Talent attraction is not about tricking people into joining your team today; it’s about being worthy of that talent every day

Want to solve the attraction / retention problem in your local/state government agency? Then do it. (You can!) There’s absolutely not “one simple trick” to make it happen. There’s no magical amount of money, no fringe benefit, no location, no one thing that will make people want to work with you, pursue your mission, and make your organization better.

It’s impossible to make your workplace attractive — unless… you want it to happen so bad you’re willing to read books, read articles, watch videos, listen to podcasts, attend conferences, talk with colleagues ad nauseum, and make the case to yourself and others that your highest mission is to make the organization worthy of attention to new hires and the old guard.

For example, here’s just one book to consider: Why Should Anyone Work Here?: What It Takes to Create an Authentic Organization

It’s like losing weight. You can lose weight on a diet, but that weight will come back when the diet ends — you cannot diet your way to permanent weight loss success. Want to change your weight and health? You must change the way you eat. Forever.

Not everyone on your team can be a “red shirt” (and that’s okay)

I originally published this post on Medium. I copied it here in May 2024 to keep it alongside my other content.

We completed some interviews last week. And in response to one candidate, I sent the following image to a fellow interviewer:

Jean-Luc Picard would like a promotion.

My “Picard in the blue shirt” reference is from a Star Trek: The Next Generation episode called “Tapestry” (S6.E13), in which captain Picard dies, but is revived by his nemesis Q and is permitted to go back in time to make different life choices, thereby avoiding his untimely death. However, Picard learns that making different — and safer — choices leads to a life he doesn’t recognize. Rather than becoming a history-making Starfleet captain, he becomes a competent science officer. He’s on the Enterprise, and is respected for his work, but he’s not a bridge officer, much less the captain.

Dissatisfied with his new blue-shirt life, Picard goes to (former subordinates) first officer Riker and counselor Troi to ask for a promotion into a command (red shirt) position, since he knows he’s capable of doing much more. It doesn’t go well:

The episode heavily suggests the best way to live is to work hard, take risks, and grab the “red shirt.” For Picard, that’s absolutely true — he’s not the Picard we know and love if he’s playing it safe.

But the red shirt isn’t for everyone.

Red vs. Blue candidates

So back to the interviews… We talked to a few candidates and the red/blue split quickly emerged.

One candidate type had taken charge in their careers, learning things, growing, and even taking some bold risks. The candidates we talked to had work experiences varying from entry-level to a decade or more, but it was evident these candidates were “owning” their work and careers personally. While they had frustrations on the job like anyone, they accepted what they couldn’t change and focused on work that moved their companies, teams, or their own careers forward. These were the “red shirts.”

The other candidate type also emerged — the “blue shirts.” These folks were smart, capable, and had accomplished some substantial work. But they were primarily passive, waiting for bosses to tell them what to do or give them permission to do things. They were more prone to complain about work they didn’t “get” to do, choices made by others, or changes they recommended, but were ignored. They definitely wanted to learn more or do more, but they didn’t want to take risks.

In the end, we liked all the candidates we talked to, and we could envision each one working out well on our team. But we were clear-eyed on what we could expect from the “red” and “blue” candidates once they arrived, and our management approach and expectations would have to be customized a bit.

Job hopping & interviewing benefits

Both red-shirt and blue-shirt candidates had histories of job-hopping, with short-ish stints in a variety of positions, which is pretty common in technology.

But there was a key difference.

Every job change for the red shirts added skills and locked in career advancements. Blue shirts changed jobs at the same rate, but they typically moved laterally and only gained skills or career bumps almost accidentally or in companies that rewarded longevity automatically.

In the interviews themselves, the red shirts also had an advantage. They typically projected more confidence and a willingness to take risks in crafting answers to our questions. That actually creates some risks for interviewers, though — it’s easy to hire a jerk or someone that overstates their skills or experiences. So you need to interview carefully.

By contrast, the blue shirts didn’t make wild claims, but they also didn’t tell their own stories that well. This also required some interviewing skill, as we had to be more aggressive in getting accomplishments out of them — they often had impressive stories to tell… they just didn’t tell them.

And to be clear, I’m not talking about the difference between introverted and extroverted candidates — most engineers we talk to and work with are introverted. Red shirts are simply more engaged with their careers, they’re willing to take risks, are more confident, and they accept they’ll make mistakes because they know they can recover from them.

Photo by hao wang on Unsplash

Good teams are purple

I would argue a good team is a mix of red and blue — a good team is a purple team. Red shirts are needed to break through barriers, refuse to accept failure as the termination of work, and take charge of problems and opportunities. But blue shirts keep the lights on. Blue shirts are the stable, long-term, loyal players that power a team through as the red shirts move on or flame out.

I’m sure there are articles out there (I can vaguely imagine some HBR pieces) that make recommendations on the “right” ratios of red to blue shirts on a team. For me, all I know is it takes both kinds of players on the team. An all-red-shirt team could be chaotic or dramatic, with everyone vying to get out in front of the team. All-blue teams would have the reverse problem, with no one stepping up to new challenges.

So keep it purple out there, people.


Disclaimer: This post does not represent the opinions or policies of my current or former employers nor any organization or person I may assist as a consultant.