Vox

Leitura de 10 min

Reframing Deficiencies as Strengths

Summary

The episode introduces a framework for reframing perceived weaknesses or underperformance in team members as potential expressions of underlying strengths. The host distinguishes between two types of underperformance: not doing enough, and doing work that doesn’t provide value to the team or manager.

The host provides concrete examples of how behaviors typically viewed as negative can be leveraged as strengths. For instance, a teammate who constantly critiques without offering solutions might excel in a quality engineering role where their natural tendency to find problems becomes valuable. Similarly, an engineer who works late hours could provide code reviews for teams in later time zones, turning a personal schedule preference into a team asset.

Further examples include perfectionist engineers who rigorously follow processes—ideal for business-critical systems requiring tight control—and engineers who take shortcuts and bundle features, potentially valuable for early-stage products needing rapid iteration. The key insight is to view behaviors not as inherently good or bad, but as tendencies that can be strategically deployed where they create the most value.

The host encourages listeners to apply this framework to themselves, examining what causes anxiety or imposter syndrome versus what feels natural and exciting. The same traits that might be labeled as deficiencies could become strengths in the right context, offering a powerful reframe for personal and professional development.

Topic Timeline

  • 00:00:00 — Introduction to underperformance and reframing weaknesses — The host introduces the episode’s theme: reframing weaknesses as expressions of strength. He outlines two common types of underperformance—not doing enough, and doing work that doesn’t provide value—and sets up the premise that many perceived shortcomings can be leveraged as strengths when viewed through a different lens.
  • 00:02:05 — Example: The constant critic as a potential strength — The host presents the first example: a teammate who always points out problems without offering solutions. Instead of viewing this as negativity, the host suggests recognizing this person’s natural ability to critique and potentially placing them in roles where finding flaws is valuable, like quality engineering. The key is to leverage what they naturally bring to the table rather than forcing them to conform to an expectation of always providing solutions.
  • 00:04:47 — Viewing behaviors neutrally and leveraging differences — The discussion shifts from labeling tendencies as negative to viewing them as neutral behaviors that can be strategically utilized. An example is given of engineers with different work schedules (early vs. late), which can be an advantage for covering different time zones or review cycles. The emphasis is on composing a team with diverse offerings rather than forcing standardization.
  • 00:05:42 — Examples of process rigor vs. speed as contextual strengths — Two contrasting engineer profiles are examined. A perfectionist who rigorously tests and follows process might be ideal for business-critical systems. Conversely, an engineer who takes shortcuts and bundles features might excel on an early-stage product needing speed. The host argues against standardizing everyone to a middle ground, suggesting instead to match these natural tendencies to the work context where they provide unique value.
  • 00:07:50 — Applying the reframe to yourself and concluding thoughts — The host encourages listeners to apply the framework to their own self-critiques and anxieties. He suggests that the things causing imposter syndrome might, in the right scenario, become strengths. The episode concludes by inviting listeners to the Developer Tea Discord community for further discussion.

Episode Info

  • Podcast: Developer Tea
  • Author: Jonathan Cutrell
  • Category: Technology Business Careers Society & Culture
  • Published: 2023-01-28T08:00:00Z
  • Duration: 00:09:34

References

Podcast Info

Transcript

[00:00:00] If you’re a manager, you probably have the opportunity, I call it an opportunity.

[00:00:21] Sometimes it feels like the burden of recognizing when someone on your team is underperforming.

[00:00:29] If you are an engineer, then you have the exciting opportunity to hear about when you

[00:00:38] are underperforming.

[00:00:40] And often this underperformance, this lack of performance, it is categorized as one of

[00:00:47] two paths, one of two kinds of underperformance.

[00:00:50] The first is not doing something, not doing enough, not practicing a particular behavior

[00:00:59] that you’re supposed to be practicing.

[00:01:02] And the second is doing something that your team or your manager is not getting value

[00:01:12] from.

[00:01:13] I phrase this very intentionally for today’s episode because we’re going to talk about

[00:01:17] reframing these weaknesses, we’ve come to call them weaknesses, reframing them to understand

[00:01:27] that these are actually usually expressions of a strength.

[00:01:32] I want to be very clear that I don’t believe that this is true for all weaknesses or all

[00:01:38] shortcomings.

[00:01:41] Certainly there are things that could inhibit you from growing in your role.

[00:01:47] There are responsibilities that if you do drop them, that’s not an expression of some

[00:01:53] other strength.

[00:01:54] But I’m going to give you this new lens for thinking about these things that we have come

[00:01:59] to call weaknesses.

[00:02:00] Let’s look at a few examples of this.

[00:02:05] Let’s imagine that you have a teammate who seems to always be pointing out issues.

[00:02:11] They’re always pointing out what’s wrong with things.

[00:02:16] They never seem to come to the table with a solution.

[00:02:21] They seem negative.

[00:02:23] This is a very common problem, but this is also very likely a potential leverage point.

[00:02:33] If this person is put in the right position, if this can be utilized as a strength rather

[00:02:40] than seen as a negative thing, rather than seen as something that detracts from this

[00:02:47] person’s ability to contribute to the team, if instead we say, okay, you know what?

[00:02:53] You’re good at finding problems.

[00:02:55] You’re good at critiquing.

[00:02:59] Can you provide critique on our ideas so that we can go and make them better?

[00:03:06] Now recognize what we’ve done here.

[00:03:08] We’ve taken the implicit expectation that’s been put on this person that in order for

[00:03:13] them to bring value to the table, they must come with a solution in mind.

[00:03:19] And instead we’ve said, okay, what are you doing naturally?

[00:03:23] What are you capable of doing naturally?

[00:03:25] What can you bring to the table that maybe nobody else is bringing to the table?

[00:03:31] You don’t have to have every piece of the puzzle, but the pieces that you bring, let’s

[00:03:37] use them to our advantage.

[00:03:40] So if you put this person in, let’s say for example, a quality engineering role, or honestly,

[00:03:45] you don’t even have to necessarily wrap a title around this.

[00:03:48] What you can do is as a team, compose your different offerings.

[00:03:56] Not everybody on the team needs to be able to provide great critique because you have

[00:04:00] someone now who does provide very good, very good critique.

[00:04:06] Now this doesn’t mean that every person should only operate in one strength area and everything

[00:04:12] else kind of falls to the wayside, right?

[00:04:15] There are still strengths that we can all work on.

[00:04:18] There are still things that you may want multiple people to have that strength.

[00:04:22] So don’t view this as having every individual hyper specialize, right?

[00:04:28] And forget all of their multifaceted strengths.

[00:04:33] We still probably want to have multiple strengths, a whole portfolio of skills that we bring

[00:04:39] to the table.

[00:04:41] But rather than viewing somebody’s natural tendencies as a negative, try to put on a

[00:04:47] new lens that takes advantage of those things.

[00:04:51] It doesn’t even have to be a negative or a positive.

[00:04:55] It may simply be a behavior.

[00:04:57] Maybe you have an engineer that likes to work later in the evenings.

[00:05:02] And another engineer who likes to work early in the mornings.

[00:05:06] This actually provides you a unique opportunity.

[00:05:11] If you want to hire in a location that has a time zone that goes a little bit later,

[00:05:16] that person may have somebody who can review their code that’s working later because you

[00:05:21] have an engineer who likes to work later hours.

[00:05:24] There’s nothing necessarily right or wrong about working early versus late.

[00:05:30] We’re looking at these things purely as behaviors and thinking about ways of taking advantage

[00:05:35] of the behaviors in the highest leverage way possible.

[00:05:39] A couple of more common examples.

[00:05:42] One example would be an engineer who seems to get caught up in process.

[00:05:48] They are perfectionists.

[00:05:50] They try to test every single part of their code.

[00:05:54] Well, do you have a part of your company that actually needs that tighter control?

[00:06:00] Do you have a part of your company that has a business critical system that can’t go down?

[00:06:07] Perhaps someone who is rigorous and thorough in their testing, somebody who follows every

[00:06:13] process to a T, they might fit well in that environment.

[00:06:18] Another example is the engineer who goes the opposite direction.

[00:06:22] They rarely write tests for all of their implemented code.

[00:06:29] Maybe they bundle up a bunch of different features in a single PR.

[00:06:33] Maybe they’re taking shortcuts here and there.

[00:06:36] This could be viewed as a negative thing if they’re breaking policy.

[00:06:39] But do you have a team that is working on, let’s say, an early stage product?

[00:06:46] Something that benefits from someone going fast and taking shortcuts?

[00:06:52] Something that doesn’t really need all of the process controls put in place?

[00:06:58] Recognizing that these kinds of natural tendencies or behaviors actually make people

[00:07:03] more suitable for different kinds of work or perhaps they can be suited to a particular

[00:07:10] team structure that coincides well with theirs or with their skills, with their natural tendencies,

[00:07:18] this is what will make those people successful.

[00:07:22] The common answer here is to try to improve the behavior, to standardize it in some way,

[00:07:28] to bring up the process for the person who is most lax and to try to turn down the process

[00:07:36] for the person who is most hardline.

[00:07:39] But it might make more sense to recognize where those things can produce unique value

[00:07:47] that is differentiated from other people.

[00:07:50] Now, importantly, apply this to yourself.

[00:07:53] What are the things that you have been self-critiquing about?

[00:07:58] What things are you self-conscious about?

[00:08:00] What produces imposter syndrome or anxiety?

[00:08:05] What are the things on the flip side that you get excited about, that feel natural to you?

[00:08:09] The things that you typically do without anybody asking you to?

[00:08:14] Things that you get good at over time?

[00:08:19] That you’re naturally inclined to improve in that particular area?

[00:08:24] Those are the things, the second, the latter half of that,

[00:08:28] are the things that are likely to be your leverage points.

[00:08:31] And if you think about all of those things that make you anxious,

[00:08:35] it’s possible that if you reframe them or put them in the right situation, the same thing,

[00:08:40] this is the amazing part, the same thing that people might call a deficiency,

[00:08:47] the same thing that you are anxious about or that’s producing that imposter syndrome,

[00:08:52] that may actually turn into a strength in the right scenario.

[00:08:59] Thanks so much for listening to today’s episode of Developer Tea.

[00:09:02] If you enjoyed this episode, I’d encourage you to join the Developer Tea Discord community

[00:09:07] as developertea.com slash Discord.

[00:09:09] It’s totally free.

[00:09:11] You have no fees.

[00:09:13] We don’t ask for anybody to pay Discord anything.

[00:09:16] Not collecting anything.

[00:09:17] You know, there’s nothing to do there other than come and join the community and talk with us.

[00:09:22] It’s developertea.com slash Discord.

[00:09:25] Thanks so much for listening and until next time, enjoy your tea.

Visão de gráfico