Process Communication Model (PCM): Persister

Transactional Analysis

Do you know at least one person that always has an opinion on a given subject? That has a strong set of values and that is the base of most of the decisions that they make? The person that is trustworthy: when they say that something is going to be done, it will, 100%? That’s Persister.

First out of six personality types in Process Communication Model (PCM), the concept created by Taibi Kahleb. You can read shortly about the concept HERE, to have a basic structure around what PCM is really about.

Today, I would love for us to have a description of who the Persister is, how we recognize this type is in the other person’s Base. Meaning that it is their first floor of personality structure, where they have most of the resources, competencies, and skills. The Base also stands for what is the most natural way of communication for the other person and through what kind of lenses they observe the world. So today we are going to discover who the Persister is, how to navigate when this person is in front of us and what to do to communicate effectively.

How do we recognize Persister?

Persister is a person who evaluates the world around them by comparing it to their values and beliefs. Their perception is opinions, and a lot of situations with Persisters relate to comparing one thing to another. How they feel, how they think and how they operate daily against the law, rules, policies, ways of working. While being around people, they’re loyal, and they value trust. They always keep promises: for a Persister it is impossible to even think about not keeping the word. If they say they do something, they are going to do it, no matter what. So, we don’t need to ask them several times a question like: “Are you going to go to do it? What is the progress of it?” because they’ll always do it (in fact, that kind of questions drive Persister crazy).

How to recognize this person if that we don’t have their personality structure yet? You can listen to the words they need.

For Persister it will be: “I believe…”, “in my opinion…”, “we should do something” or …shouldn’t do something”, “I trust…”, “the important thing for me is…”, “the crucial thing is…”.

They say those words because they see the world through the lenses of opinions and values: that’s how Persister is the most visible. Of course, we are talking about being in OK-OK zone. It’s about having an opinion, but also always having a good intention. It’s not about pushing the opinion no matter what or aiming to hurt others.

They have an opinion on every single subject and even if they don’t (i.e., they’re not interested in something), they have an opinion on it. Like: “Ok, so I’m not into politics because it really doesn’t interest me: I don’t want to waste my time on that subject”. Based on that example, we can see that there is always an opinion, even if at the first sight there’s none. What is also important that Persister doesn’t have any problem with saying those opinions out loud. And it’s not about being rude: it’s about being persistent, having a voice that matters (in professional and/or private life). Of course, HOW the opinion is communicated is important (it needs to be said from the OK-OK perspective). If it’s not – it’s another part of the story.

What do Persister need in communication?

The Persister needs communication process where they have a chance to express their opinions. Extremely important for them as well is to have a partner to exchange the opinions with.
To be efficient in communication with Persister, we need to use requestive channel of communication. That means that we need to ask questions about their opinion on certain subjects. For example, when we want to delegate a task, so a chosen employee covers it, the great approach will be telling them about it and then ask about their opinion on it. “Okay, here is a task X, what’s your opinion on it? What do you believe is important to complete it efficiently? What kind of value we can bring by covering this task together?” Asking that kind of questions is something that we can do to get in contact with Persister. Once they are on board, we can talk about the details (scope, deadline, support, required learning etc.).
They value Democratic interaction style. It means that they are really good in making decisions in cooperation with others. They like discussions, brainstorming sessions, they value feedback. And the worst thing that we can do while getting in contact with Persister is to use directive communication channel. Telling them what to do without even asking is something that they hate. When they have an autocratic person on the other side of the conversation, they go into aggression behaviors. By being in that zone there is a huge possibility that they’re going to attack other people. So democratic interaction style and requestive communication channel is a key to success in getting on the same page with that person.
Persister seek to answer the existential question: am I trustworthy? It’s good to feed that question, especially when we see that Persister is under some kind of stress or pressure. For them the following equation is the only truth.

I’m trustworthy = I’m valuable as a person

Motivational needs attached to this PCM type are recognition of principled work and recognition of conviction. It’s important to know it, since when those needs are not met, Persister goes into distress and loses access to their skills, abilities to think clearly. Recognition of principled work means that we are seen as people for what we deliver at work and this delivery is compliant with the rules, ways of working in a certain organization, that is done by the book, or in alignment with a certain process or structure. Recognition of conviction means that we are appreciated with our values, opinions, and beliefs about a given topic. We can feed both of those needs by emphasizing what this person did – not who they are (this is the need of Harmonizer), but what they delivered, by being focused on those two criteria.

When do we know that Persister is in distress?

What does to be in distress mean? Being a distress means that we don’t have our motivational needs covered and we go into a sequence that is aligned with certain PCM type. So, if you have a Persister on the other side of the communication process and their needs are frustrated, they go into distress, you will see 3 steps of the sequence.

Driver: you need to be perfect for me. On the first level of distress, Persister will focus on things that are not good enough, somehow not perfect enough. They will be more into looking for mistakes, than appreciating the things that are done well. We can observe using big, complicated words, or asking complex and difficult questions. When we see that kind of behavior, we can offer recognition, and then proper, requestive communication channel and perception of opinions (i.e. “I respect your work aligned with the highest standards. I know that thanks to that our team scores results that are above average. What is your opinion on an approach X that I invented to do it faster, without losing our quality?). BOOM! We’re going back to OK-OK zone and we can talk with access to the whole Persister’s skillset.
Attacker Mask. If we don’t stop the driver, we go into the second level of distress, which is the mask. On the first level it’s quite easy to take the person out of it, but on the second level is not a piece of cake. Like in a real life: when a person has a mask on their face, sometimes it’s even hard to recognize them. No bueno. Persister with a mask on attack others for not having “proper’ values and live by them i.e. “You don’t care about out customers!” or “You should be more committed!”. They can push their believes on others, treating it like one and only. When we see that kind of behavior, the approach is the same as in the driver situation: addressing the corresponding motivational needs.
Cellar: Despair. It’s time for a payoff. The first and second level of distress convinced Persister that everything and everyone is hopeless. There are no people with values, nobody cares about work according to the principles, processes, and ways of working that are important to have the highest quality of deliveries. Solution? Still the best invitation to come back to OK-OK zone is to offer covering the corresponding motivational needs. It can be extremely hard, yet doable. And we need to remember that the decision about accepting our invitation or not is on the other person, not us.

Being in distress means that we don’t think clearly. When it happens, we don’t have access to our skillset, abilities to deal with different (especially stressful and difficult) situations, we can’t act accordingly (even if we rationally know how to do it). That’s why it’s so important firstly to come back to OK-OK, to our Base, and then – once we are there, go and deal with the situation. That kind of approach is always going to work, regardless of the PCM type. It’s worth to remember the sequence, since it is repetitive. By training ourselves in recognizing patterns we train our muscle of reacting accordingly, without going into distress ourselves. The mask invites the mask: meaning that behavior under distress will have influence on us, and even if we are in OK-OK zone, we can go into the dark side. Being aware of what’s happening gives us tools to protect ourselves and support others in getting into better place.

The bottom line

Persister is a great person to cooperate with. When they say that they’ll do something, we can be sure that will happen, no matter what. We don’t even need to doublecheck: for Persisters it’s impossible to not deliver the things that we agreed on, it’s in their DNA to do it. Their strong principles, values, and a high-level need to be trustworthy make them great partners in crime.

Of course, while being in distress, they lose access to those resources and go into not so shiny place. It requires more awareness, being mindful what happens with us (if we are Persisters in Base), and other people (when Persister is on the other side of communication process). So, I invite us all to observe those behaviors described in the article starting today. It can help us more than we think, regardless of the type of relation, context, or situation that we are in. It’s always worth to develop in this area.

PS. As a first exercise after reading this article, you can count how many times I expressed an opinion throughout the whole text (my base is Persister, so it should be quite visible).

Udostępnij

Komentarze

0 0 votes

Article Rating

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

5 January 2025 No Comments

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

24 December 2024 No Comments

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

29 November 2024 No Comments