Lemanskills.com

Process Communication Model (PCM): Rebel

“Wooooooow, it’s soooo aweeeesome!!!”, “I like this idea, and this one sucks.”, “It’s plastic bombastic!”

Do you know a person or two who speak that way? And yes, I mean an adult, not a kid or a teenager.

The person that reacts really vividly to what’s happening, that says openly whether they like or dislike ideas, clothes or food?

That’s the Rebel.

The fourth out of six personality types in Process Communication Model. We’ve started the story about PCM HERE and then we’ve described Persister, Thinker and Promoter.

Today we’re adding another piece to our PCM puzzle, so we understand different people once we meet them, have them as team members or stakeholders in different circumstances (professional and private). For those of us who has little Rebel energy, this one can appear like a crazy person. Why? Let’s unpack it today!

 

How do we recognize Rebel?

 

Rebel is a person who experience the world through the lens of reactions. Most of the time, they react right away with a strong “like / dislike” statement. They either go for it or leave it and never start doing something. They have this free child energy that allows them to feel joy, excitement, experience the world with the enthusiasm that we often loose along the way.

How to recognize a Rebel in the Base of personality? Again, the easiest way to make a strong hypothesis is to look for the key words that the person uses the most.

For Rebel it will be: “Wow!”, “Awesome!”, “I like / dislike this!”, “Cool!”, “Amazing!”, “Oh, how disgusting!” They will use slogan words quite often as well.

They say all that because they want to invite us to express our own reactions. It’s because they need to be in authentic contact with others, that’s how they feel that they belong and are accepted. They are extremely creative, thanks to their open-minded heads. A Rebel can be a great member of a team (or project team) at the very beginning of the initiative, when we brainstorm. They can figure out a big number of ideas, sometimes super weird or that seem impossible to implement. Those ideas that i.e. Thinkers or Persisters would never come up with.

The recognition of Rebel r is also easier when we look on their non-verbal communication: most of the time their face is extremely emotive, with a lot of mimics on it. Their voice is changing, modulating to express the proper emotion and reaction they aim for. They move their body a lot, using a lot of gestures to emphasize what they want to express.

If you see and hear it, that’s a strong indicator that there’s a Rebel in the Base on the other side of the communication process. How to use it to get along with that kind of person?

 

What does Rebel need in communication?

 

  • The Rebel needs communication process where they have a chance to express their reactions. Extremely important for them as well is to have a space, where they can go into contact with others, by exchanging those reactions.
  • To be efficient in communication with Rebel, we need to use emotive channel of communication. It means that we need to reach to those higher levels of energy we have (for some of us it can be pretty demanding) to get into the positive exchange as a start of a conversation. That means that asking questions or directly saying what’s there to be done won’t work in Rebel’s case. How to do it? Using the same example as before: when we want to delegate a task, so a chosen employee covers it, the great approach will be energizing the conversation first. “Hi Bob, it’s dope to see you! Did you see this game on Saturday? OMG it was nuts! (you talk for a while so the Rebel can give their reactions too). And by the way, I have this task, it’s pretty awesome, you up for a mission?” For them it needs to be fun, even if for us it seems ridiculous. Once they are on board, we can talk about the details (scope, deadline, support, required learning etc.).
  • They value Laissez-faire interaction style. It means that they need freedom, autonomy and space to be creative and deliver things. One of the worst things that we can do while getting in contact with Rebel is to be too directive, asking questions, especially a lot of them won’t work very well too. Yes, they need structure and clear contract on what’s there to be done and for when but too much of a control or asking them in detail what they do will bring us the opposite results.
  • Rebel seek to answer the existential question: am I accepted? It’s good to feed that question, especially when we see that Rebel is under some kind of stress or pressure. For them the following equation is the only truth.

 

I’m accepted by others = I’m valuable as a person

 

  • One motivational need attached to this PCM type is contact. It’s important to know it, since when those needs are not met, Rebel goes into distress and loses access to their skills, abilities to think clearly. Contact means that we are going actively in positive interaction with other people. We are seen as important part of the conversation, exchange of ideas, and sometimes just a person who can change the temperature in the room for the better. We can feed the need of contact by getting into the conversation or positive exchange, even when we don’t feel like it at the moment or it doesn’t seem logical.

 

When do we know that Rebel is in distress?

 

Just a reminder: distress is negative stress, that costs us (and our environment) something. We are in distress when our motivational needs are frustrated and to cover them (in a really bizarre way), we into the distress sequence. How does is look like for a Rebel?

  1. Driver: I need to try hard for you (meaning: I’m OK only if I try hard). On this level, Rebel often says that they don’t understand things, by saying that they just don’t get it. That mechanism invites others to think and resolve issues for them (since they don’t really get it). When we see that kind of behavior, we can offer positive contact by saying something like: “Oh man I hate when it happens to me! C’mon, let’s figure it out together!”. That kind of reaction will take Rebel out of the rabbit hole and get them back to OK-OK space.
  2. Blamer Mask. Like Promoter, Rebel also wears a blamer mask on the second level of distress. The difference is that Promoter blame others that they are not strong or immune enough to conquer the world. For the Rebel it’s more vengeful, they blame others for things that i.e. they didn’t deliver. They always find an external circumstance (a.k.a. other people) that are responsible for the lack of effect or work delivery. Again: they do it because they lack positive contact and that is an approach they choose to get in any contact, even if it’s negative like that one. It’s also their way to not take responsibility which is their issue in overall.
  3. Cellar: At the end, Rebel is going into the mode: “Watch me! I’ll show you and then you remember!”

As you can see, being in distress is an algorithmic body and brain response to not having covered the motivational needs. This sequence is repetitive, happens every time that a person is triggered in any way. The whole sequence can last 30 seconds (literally) or can be longer. The more frequently we go through the whole path (3 steps), the more “coupons” we collect to pay them out.

That’s why it’s so important to stop the vicious cycle as soon as we realize that it starts: the sooner, the easier it will be. And remember that we can cover the needs on our own, but also, we can ask the people around us for support. We can make a little contract with people in our environment (private and work) that stands: “if you see that X and Y behavior is starting within myself, please react with a proper needs’ coverage. That way I will come back to myself faster, and nobody gets hurt”. It’s especially important on the Mask level, since when we are there, often we don’t think clearly, so it’s super hard for us to cover our own needs properly.

 

The bottom line

 

The Rebel is another great player in a team. Especially when you need creativity, generating ideas, solving problems when others are stuck. Their beautiful brains can create so many ways to do so, that may seem a little outrageous or crazy for others (especially Thinkers and Persisters, as mentioned above). Because they have a high level of energy, Rebels can be perceived like ADHD (non-clinical), with endless source of optimism, joy or enthusiasm for others.

In the dark world that we often experience, having those people is especially valuable. They make us laugh, sometimes see a different perspective or get a sparkle that will move our thinking and doing into direction that we’ve never saw before.

Of course, under stress it’s harder since the Rebel won’t deliver on time, will blame others that they didn’t do their job and will find all the excuses in the world. But after getting over with that behavior and going into OK-OK zone, we can create an extraordinary value.

That’s what the Rebel is for.

Udostępnij

Komentarze

0 0 votes
Article Rating
Subscribe
Notify of
0 komentarzy
Oldest
Newest Most Voted
Inline Feedbacks
View all comments

Czytaj także

Leadership

10 Ways to Get Your Time Back: Practical Tips for a Tech Leader

As a Tech Leader, your day is likely filled with endless meetings, urgent emails, project deadlines, and unexpected crises. It’s easy to feel like there’s never enough time to focus on what truly matters—whether that’s strategic thinking, team development, or even your own well-being. But here’s the good news: with a few intentional changes, you can reclaim your time and focus on what drives real impact. This isn’t about pretty theories or abstract advice. Below, you’ll find 10 practical, actionable tips that you can start implementing today to get your time back. Interested? Let’s get to it!     #1 Audit Your Calendar   Your calendar tells the story of where your time goes—and often, it’s not a pretty picture. Start by reviewing your calendar for the past two weeks. Ask yourself: Which meetings were truly necessary? Could some have been shorter? Were there meetings I didn’t need to attend at all as a leader of my team? Depends on the answers, make some shifts. Move meetings around, if you have influence on them: put them in the time of the day that you’re not in your genius zone. Use the calendar as you source of power, not a thing you are a slave of. Actionable Tip: For every recurring meeting on your calendar, apply the “zero-based budgeting” approach. Assume the meeting doesn’t need to exist unless there’s a compelling reason to keep it. For meetings you do keep, limit them to 25 or 50 minutes instead of the standard 30 or 60 minutes—this will force more focused discussions and give you breathing room between calls.   #2 Delegate Like a Pro Leader   Tech Leaders often fall into the trap of trying to do everything themselves—whether it’s troubleshooting a technical issue or reviewing every line of code. But delegation isn’t just about offloading tasks; it’s about empowering your team and creating space for you to focus on higher-level priorities. Actionable Tip: Use the “3D Framework” for tasks: Do it, Delegate it, or Delete it. If a task doesn’t absolutely require your expertise, delegate it to someone who can handle it. And if it doesn’t add value, delete it altogether. Make sure of good contracting around the delegation though: it needs to be clear, including context, checking on the skillset of the person who’s going to get the task. Be smart here; don’t assume: ask.   #3 Batch Similar Tasks Together   Switching between tasks—like coding, answering emails or Slack / Teams messages, and attending meetings—can drain your mental energy and waste time. Instead, group similar tasks together and tackle them in dedicated blocks of time. Actionable Tip: Create “themed” days or blocks of time. For example: – Monday mornings: Strategic planning – Tuesday afternoons: One-on-ones with team members – Friday mornings: Deep work on a long-term project When you batch tasks, you reduce context-switching and increase focus. Let’s say it once for good: there’s no such thing as multitasking. You can switch between tasks really quickly, but it has its cost. Reduce it, be more focused and you’ll see the difference in your efficiency and energy level as a leader.   #4 Say “No” More Often   Every time you say “yes” to something, you’re saying “no” to something else—often your own priorities. Learning to say “no”, or “yes, and…” is one of the most powerful ways to protect your time as a Tech Leader. Actionable Tip: When someone asks for your time, don’t respond immediately. Instead, say: “Let me think about it and get back to you.” This gives you space to evaluate whether the request aligns with your goals. If it doesn’t, politely decline or suggest an alternative solution.  Remember about being in OK-OK space: you don’t want to be rude or aggressive; boundary setting is not about hurting others, it’s about protecting yourself.   #5 Leverage Asynchronous Communication   Not every conversation needs to happen in real-time. In fact, asynchronous communication can save you hours each week by reducing unnecessary meetings and interruptions. Actionable Tip: Use tools like Slack, MS Teams, or Loom to communicate asynchronously. For example, instead of scheduling a meeting to discuss a project update, record a short video or write a detailed message outlining the key points and next steps. Bonus Tip: Set clear expectations for response times in asynchronous channels (i.e., “respond within 24 hours”) so everyone stays aligned without feeling pressured to reply instantly.   #6 Automate Repetitive Tasks   If you’re spending time on repetitive tasks that could be automated, you’re leaving valuable hours on the table. Automation isn’t just for developers—it’s a key productivity tool for all of us, regardless of our role in the organization. Actionable Tip: Identify one repetitive task you handle weekly (i.e., generating reports, scheduling meetings, answering emails) and automate it using tools like Zapier, IFTTT, or custom scripts. Example: Automate status updates by integrating project management tools like Jira or Trello with Slack so your team gets real-time progress updates without manual intervention.   #7 Create Decision-Making Frameworks   Decision fatigue is real—and as a tech leader, you’re probably making dozens of decisions every day. And we have a limited decision capacity: we make around 35,000 decisions daily, but less than 100 are optimal. Creating frameworks can help streamline this process and free up mental energy for more important work and more capacity for better decisions. Actionable Tip: Develop simple decision-making criteria for recurring situations. For example: Hiring decisions: Does this candidate have at least 70% of the required skills? Project prioritization: Does this initiative align with our top three business goals? Task selection: Does this task bring me closer to the OKRs I have on my list for this quarter? By standardizing decisions, you’ll spend less time deliberating and more time executing.   #8 Adopt a “Less is More” Leadership Mindset   In Tech Leadership, more isn’t always better—more features, more meetings, more initiatives can lead to diminishing returns. Focus on doing fewer things exceptionally well rather than spreading yourself too

Czytaj dalej
Leadership

Why Habits Are Better Than Goals: A Guide for Leaders

As technology leaders, we live in a world driven by deadlines, KPIs, and ambitious goals. We’re taught to set objectives and measure progress. But what if I told you that focusing on habits rather than goals might be the game-changer you’ve been looking for? Especially if you’re struggling to find time for your own professional development or noticing low engagement within your team, shifting your mindset to prioritize habits could transform not only your leadership but also your entire organization. Let’s explore why habits are more powerful than goals and how they can help you lead with greater impact. The Problem with Goals   Goals are seductive. They promise a future where everything is better: you’ve mastered a new skill, your team is more engaged, or you’ve finally achieved that elusive work-life balance. But here’s the catch: goals are outcome-focused. They emphasize the “what” rather than the “how”. For example, let’s say your goal is to improve team engagement. You might set metrics like increasing participation in meetings or boosting employee satisfaction scores. But once you hit those targets, what happens next? Without a system in place, the progress often stalls or even reverses. Goals also have an inherent flaw: they’re temporary. Once achieved, they leave a void. This is why so many of us experience the post-goal slump: a sense of “what now?” after crossing the finish line. Moreover, as busy technology leaders, goals can feel overwhelming. When your calendar is already packed with back-to-back meetings and project deadlines, adding another goal to the mix can feel like just another task on an endless to-do list.   Why Habits Are the Better Alternative?   Habits, on the other hand, focus on the process. They are small, consistent actions that compound over time to create meaningful change. Instead of chasing a distant outcome, habits anchor you in the present and guide your daily behavior. Here’s why this matters: Habits Build Identity. While goals are about achieving something external, habits shape who you are. For example, instead of setting a goal to “become a better communicator,” you could develop the habit of asking open-ended questions during one-on-one meetings. Over time, this habit reinforces your identity as a leader who listens and connects deeply with their team. Habits Are Sustainable. Unlike goals, which have an endpoint, habits are ongoing. They create a foundation for continuous improvement without requiring constant resets. A habit like setting aside 15 minutes every day for professional reading or reflection becomes part of your routine:no extra mental energy required. Habits Reduce Decision Fatigue. As a leader, you make countless decisions every day. Habits automate certain behaviors, freeing up mental bandwidth for higher-priority tasks. For instance, if you establish a habit of starting each morning by reviewing your team’s priorities, you don’t have to waste time deciding how to begin your day: it’s already decided for you. Habits Drive Engagement. When it comes to team dynamics, habits can be contagious. If you consistently model behaviors like active listening or celebrating small wins, your team is likely to adopt those practices as well. Over time, these shared habits create a culture of engagement and collaboration without requiring constant top-down interventions.     How to Build Habits That Stick?   Now that we’ve established why habits are so powerful, let’s talk about how to build them effectively. Here are some practical steps tailored for busy technology leaders: #1 Start Small One of the biggest mistakes people make is trying to change their entire routine overnight. Instead, focus on one small habit at a time. For example, if you want to prioritize professional development, commit to reading just one article or watching one TED Talk per week. Once this becomes second nature, you can build on it. #2 Anchor New Habits to Existing Routines Habits are easier to establish when they’re tied to something you already do regularly. For instance, if you want to foster better communication with your team, make it a habit to ask for feedback during your weekly check-ins. The check-in is already part of your routine; now it has an added layer of intentionality. #3 Focus on Systems, Not Outcomes Instead of obsessing over results, concentrate on creating systems that support your desired behavior. For example, if you want to encourage innovation within your team, implement a habit of dedicating 10 minutes at the end of each meeting for brainstorming new ideas. #4 Track Progress and Celebrate Small Wins While habits don’t rely on external validation like goals do, tracking your progress can still be motivating. Use apps or simple checklists to monitor consistency and celebrate milestones along the way. #5 Be Patient and Consistent Habits take time to form: research suggests anywhere from 21 days to several months depending on the complexity of the behavior. Don’t be discouraged by setbacks. Focus on consistency over perfection.   The Ripple Effect of Habits in Leadership   When you embrace habits as a leader, the benefits extend far beyond your personal growth: they ripple out to your entire team and organization. Here are some examples: Improved Team Engagement. By modeling habits like regular recognition or transparent communication, you create an environment where team members feel valued and motivated. Greater Innovation. Small habits like encouraging questions or dedicating time for creative thinking can spark breakthroughs that drive your projects forward. Stronger Relationships. Consistent habits like active listening or showing empathy build trust and strengthen connections with both colleagues and stakeholders. Most importantly, focusing on habits helps you lead by example. It shows your team that growth isn’t about chasing lofty goals but about showing up every day with intention and purpose.   A Challenge for You!   As you reflect on this article, I want to leave you with a simple challenge: choose one habit that aligns with your leadership vision and commit to practicing it consistently for the next 30 days. It could be as simple as starting each day with five minutes of mindfulness or ending each meeting

Czytaj dalej
Leadership

Communication Intelligence (CQ): A Key to the Effective Leadership

In the ever-evolving landscape of work, where collaboration and innovation are necessary to survive on the demanding market, one skill stands out as a game-changer: Communication Intelligence (CQ). As a tech leadership expert and someone deeply invested in helping leaders and teams create environments where people thrive, I cannot stress enough the importance of mastering CQ. It’s not just about talking or listening; it’s about understanding, tailoring, and connecting. Let’s dive into what CQ is, why it matters, and how we can build this skill: both as leaders and team members.   What Is Communication Intelligence (CQ)?   At its core, Communication Intelligence (CQ) is the ability to adapt your communication style to connect effectively with others. It’s about being aware of your own communication tendencies while recognizing and responding to the diverse preferences of those around you. Think of it as emotional intelligence (EQ) but focused specifically on how we exchange information, ideas, and emotions. CQ involves empathy, adaptability, and clarity. It’s not just about what you say but how you say it—and how it’s received. Mastering CQ means being intentional in your interactions and ensuring that your message resonates with the person or people on the other side.   Why Is CQ Essential for Leaders and Team Members?   In my work with leaders and teams, I often see how miscommunication can ruin even the best intentions. A lack of CQ can lead to misunderstandings, conflict, and disengagement. On the flip side, strong CQ fosters trust, collaboration, and alignment: key ingredients for both thriving teams and great business results. Here’s why CQ is crucial: #1 For Leaders: they set the tone for communication within their teams. If a leader lacks CQ, they risk alienating team members, failing to inspire, or unintentionally creating a culture of fear or confusion. Leaders with high CQ can tailor their messages to motivate diverse individuals, navigate difficult conversations with grace, and build an environment where everyone feels heard and valued.   #2 For Team Members: in a team setting, CQ helps individuals collaborate more effectively. When team members understand each other’s communication styles, they can avoid unnecessary friction and build stronger relationships. High CQ also empowers individuals to voice their ideas in ways that resonate with others, fostering innovation and mutual respect. Understanding what high CQ looks like (and what it doesn’t) is key to developing this skill. Let’s explore some examples and anti-examples.   Examples of High CQ Behaviors: – active listening: truly hearing what someone is saying without interrupting or jumping to conclusions to soon, – tailoring messaging: adapting your tone, language, or delivery based on the audience. For instance, explaining a technical concept in simple terms for a non-technical stakeholder, – understanding in action: acknowledging someone’s emotions and needs before moving to problem-solving. For example, saying, “I can see this situation has been frustrating for you” before diving into solutions, – clarity in feedback: providing constructive feedback that is specific, actionable, and framed positively. And what’s even more: giving people space to take it in and make a decision what they want to do with it (take or discard), – proactive negative conflict resolution: addressing misunderstandings early rather than letting them grow and eat people alive. And remembering that not all conflicts are bad (actually a fear of conflict is one of the 5 Dysfunctions Of The Team by Patrick Lencioni).   Anti-Examples of Low CQ Behaviors: – interrupting or talking over others: this signals a lack of respect and can shut down meaningful dialogue. It also means that you don’t care about the other person, or anything they say or think, – one-size-fits-all communication: using the same approach for everyone without considering individual preferences or needs. There’s only 17% of chances that the person next to you prefers your communication base. That’s why listening and tailoring is so important: to get the stakes higher than that, – ignoring non-verbal cues: overlooking body language or tone that suggests someone is uncomfortable or disengaged. We have 4 things we can observe: mimics, ton of voice, gestures and posture. Ignoring those non-verbal imformation is going to cost us a lot, – defensiveness in feedback: reacting negatively when receiving constructive criticism instead of seeking to understand, ask more questions, be curious about what the other person wants to say to me, – avoiding difficult conversations: failing to address issues directly, leading to confusion or resentment. And the further it goes, the worse it becomes: it’s really difficiult to stop the huge snowball. So what we can do to avoid those anti-examples?   Use PCM to Build it!   One of the most effective tools I use when working with leaders and teams on CQ is the Process Communication Model (PCM). PCM provides a framework for understanding different personality types and their communication preferences. It’s like having a map that helps you navigate the complexities of human interaction. So why PCM is a good idea to support buildling a high CQ level? It gives you bigger self-awareness: start by identifying your own dominant personality type. This helps you understand your natural communication style and potential blind spots. With whom it’s super easy to go with and when it will be a bigger challenge. It equips you with higher ability of observation: pay attention to the verbal and non-verbal cues of others to identify their preferred communication style. For example: – A Thinker might appreciate detailed agendas and logical arguments. – A Harmonizer may respond better to warmth and emotional connection. It gives you a reason to adapt more: tailor your communication to match the other person’s style. If you’re a Promoter speaking with an Imaginer, slow down and give them time to process rather than pushing for immediate action. It shows you how to practice under stress: PCM also teaches us how stress impacts communication. For instance, under stress, a Thinker might become overly critical, while a Rebel might resort to sarcasm and manipulation. Recognizing these patterns helps us respond constructively rather than

Czytaj dalej
0
Would love your thoughts, please comment.x
()
x