top of page

What a Strengths Workshop Should Actually Change at Work

Sep 19
7 min read

Training covers a lot of ground, and strengths-based work sits in its own particular corner of it. The same quiet failure keeps turning up there. Everyone leaves the room feeling understood, and almost nothing changes in the weeks that follow. The feedback forms score well. The conversation in the corridor afterwards is warm. Then people go back to their desks and do exactly what they were doing before, only now with a nicer vocabulary for it.


That is not a strengths workshop working. That is a strengths workshop performing, and the two are easy to mistake for each other from the front of the room.


The distinction matters because organisations keep buying the version that performs well, because it is easier to sell and easier to sit through than the version that actually produces something. A session built around comfort and identity will always score better on satisfaction than one built around friction and utility. People enjoy being told what they already suspect about themselves. They enjoy it a great deal less when a workshop surfaces exactly why two colleagues cannot work together, or why a manager has quietly become the bottleneck for every decision on their team. That second kind of discomfort is where the value actually sits.



Why comfort has become the default

Identity-based framing is seductive because it asks so little of anyone in the room. You take an assessment, you learn your top strengths, you nod along as the facilitator describes you with reasonable accuracy, and you leave. Nobody has to have a difficult conversation. Nobody has to admit that the way they currently work is costing the team something. The session is genuinely pleasant, and pleasant sells well.


The harder version asks people to look at where their strengths are actually landing, not just what they are. That means naming, specifically, where a person's natural way of working is producing friction rather than value. It means a manager hearing that their instinct to decide everything themselves is the reason their team has stopped bringing them problems early. It means two colleagues realising, in the room, that one needs time to think and the other processes ideas out loud, and that neither has adjusted for the other in eighteen months of working together. That is genuinely uncomfortable to sit through. That discomfort is often where the more useful work actually begins.


A strength is not automatically useful

One thing I think gets misunderstood constantly is the idea that recognising a strength is the same as making it useful. It is not the same thing at all. A strength does not create value simply because someone has it. Its value depends on the role, the situation, and what the business actually needs from that person right now. Someone whose instinct is to move fast and create momentum is an asset in a team that is stuck. The same instinct becomes a liability in a team that needs careful, considered execution and has already made its decisions. The strength has not changed. What the business needs from it has changed instead.


This is where a lot of strengths work quietly falls short. It treats the assessment as the endpoint rather than the starting point, handing someone a profile and trusting them to work out the application themselves. Assessment clearly has value here. Research from DDI's 2023 Global Leadership Forecast found that 45 per cent of leaders want more assessment to inform their development. But wanting more insight is not the same as knowing what to do with it once you have it. A tool like Strengthscope can show someone where they stand, and when it is built properly into a programme rather than run as a one-off exercise, it gives the work something organisations genuinely value: real data behind the session, not just a facilitator's read of the room. Development starts when that shows up in what they actually do differently, in the room, under real conditions. Handing someone a report and leaving them to make the connection is not development. It is data collection.



What friction actually looks like in the room

A workshop that is doing its job does not stay comfortable for long, though the discomfort is rarely a clash between people. That is not something I see often in the room, and I would not want to suggest otherwise. What I do see, regularly, is something quieter and more individual. Someone looks at their own results and their face changes. You can watch the moment happen: the data lands, and they are suddenly holding it up against the role they are actually in, turning over what fits and what they could probably be doing differently.


That is not friction in the obvious sense, but it is not comfortable either, and it is where the real work of a session tends to start. The friction that does show up tends to come from somewhere less expected than conflict. People want to talk about themselves. Once someone recognises something true about how they work, they want to say more about it, and so does everyone else in the room at the same time. A session that has genuinely landed can tip into that kind of overstimulation, which is a far better problem to have than a room that stays polite and disengaged throughout, but it still needs managing, or the insight never gets turned into anything.


None of this gets fixed by everyone learning their top five strengths. It gets fixed by turning that individual recognition into something concrete before the room empties: a decision about where someone focuses differently, what they stop doing, or what they finally ask for at work. If a workshop does not end with something concrete that people agree to test or change, it risks becoming a pleasant morning rather than a meaningful intervention.


At a team level, the same principle extends further. Strengths do not operate in isolation at work. They meet other people's strengths constantly, mostly without anyone naming it. One person's pace affects how much thinking time a colleague actually gets. One person's need for independence meets another person's need for context. In that setting, the useful question is rarely just what our strengths are. It is closer to what happens when our strengths meet, which is exactly where a team session earns its place alongside individual ones.



The design work nobody in the room sees

Before I write a word of content, I want to know who will actually be in the room, what they are carrying in with them, and what they are hoping will be different by the time they leave. A workshop written for a general audience and adapted on the day is a different thing entirely from one built around a specific group from the start, and it shows, even when nobody in the room could tell you exactly why.


I recently built a strengths-based training programme for a group of early-stage business owners, and the part that actually determined whether it worked had almost nothing to do with the day itself. The final output was a presentation and a companion workbook, built to function as one experience rather than two separate materials that happened to be used on the same morning. Every activity in the workbook tied back to a specific point in the presentation, so nobody in the room was ever guessing what they were meant to be doing or why.


Getting there took several rounds of refinement. I grounded the material in established research on self-efficacy and how people compare themselves to others, because I wanted the content to hold up under scrutiny, not just feel good in the moment. I tested pacing against how the session would actually run with real people completing exercises in real time, and I would rather cut an activity that was merely interesting than one that was genuinely doing something for the room. I checked every cross-reference, because the kind of detail that is invisible when it is right becomes glaringly obvious the moment it is wrong.


None of that shows up in the room. What does show up is whether the session moves at the right pace for the specific people in it, whether the language lands without anyone needing it explained, and whether each exercise builds on the last rather than sitting beside it. That is the actual craft behind a strengths-based workshop that works, and it is almost entirely invisible when it has been done properly.

Organisations rarely see this part, and that is exactly why they underestimate it. A workshop that looks simple to sit in usually took a disproportionate amount of design discipline to get there.



What organisations misunderstand about the outcome

The mistake organisations can make is treating the workshop itself as the intervention. It never really was. The workshop is where the friction gets named. The intervention is what happens afterwards, in how workflows get redesigned, how projects get reallocated, and how people are actually managed differently as a result of what surfaced in the room. Our Team and Leadership Workshops are built around this distinction specifically, with the session structured to produce agreed changes rather than a shared vocabulary and a warm afternoon.


Without that follow-through, a strengths workshop becomes a one-off event that people remember fondly and act on for about a fortnight. With it, the same investment becomes the starting point for genuinely different ways of working, delegating and managing across a team.


What to ask before you book one

Before agreeing to a strengths workshop for your team, be honest with yourself about what you actually want to change. If the aim is simply connection and shared language across a team that already functions well, a lighter session can be entirely appropriate. If morale is low because of workload, management behaviour, or a restructure that hasn't been properly explained, a comfortable strengths workshop will not fix that, and it can look like the organisation is avoiding the real problem. If the issue is a specific, ongoing one- slow decisions, a bottlenecked manager, a team working hard but at cross-purposes- the session needs to be built to force that conversation, not soften it.


Ask what will happen differently in the six weeks after the session, not just how people will feel on the day. Ask whether the facilitator is willing to name friction between specific individuals if that is what the room needs, rather than keeping things comfortable for everyone. If you already know which team or which problem needs the work, that is a conversation about Team and Leadership Workshops. If you are not yet sure where the friction actually sits, a Workforce Potential Review is often the better place to begin.


A strengths workshop that only makes people feel good has stopped short of the real work. The test is not how the room felt when it ended. It is whether, six weeks later, you can point to something genuinely different: a decision made differently, a responsibility redistributed, a meeting redesigned, or a conversation finally had because of what surfaced in the room. If nothing has changed, the workshop produced insight. It did not yet produce development.


 

By Paula Donnan

Strength at Work | Better judgement. Stronger leadership. Higher performance.

If this is affecting you, book in for a free 30-minute initial briefing to discuss the way forward.


Initial Briefing
30min
Book Now
Team and Leadership Workshop - Full Day
Buy Now

Comments


bottom of page