PCM: Communication Channels

Transactional Analysis

When I was describing all 6 Process Communication Model (PCM) types, it dawned on me that if I want to find one aspect of it that interests me, I need to go into each article and look for one part. And there are some of those, that are more important to dig deeper into, a good example is the aspect of communication channel.

So I’ve decided that I’ll go into this directing to simplify and edit this experience for you: to go into some aspects of PCM, with practical examples. Hope that’ll be useful and will give you all the impulse to start using it in real life.

What Are Communication Channels?

Before we go into the details, let’s start with answering this questions: what a channel actually is?

Communication channel is the way we build a sentence we want to push forward the other person (doesn’t matter if it’s a written or verbal communication). Surprisingly it really does matter if we put a question mark or a period at the end of the sentence. It matters so much that most of the time it has a huge influence on if the communication will go through or not (will be efficient or will lead to a misunderstanding).

What do I mean by that? Take a look on those examples (purposefully not business-related):

What do you think about this painting?
Please tell me what you think about this painting.
Oh man, what a painting, I’m sure it kills us both just from looking at it!!!!!
Thank you for being here with me to marvel this painting, I’m more than happy to hear your impressions on it.

Do you see the difference? We all have one dominant preference of getting and using the channel, depends on our personality base. When you look on those sentences: which one is the most comfortable for you? Depending on which one you choose, it’s a strong indicator of your base.

Requestive Channel

The first sentence is a great example of a requestive channel. As you can see, the idea is simple: ask a question (so a sentence with a question mark at the end of it).

Using the knowledge that you already have, you can see the difference between the questions that we can ask towards 2 bases that will prefer this channel: Thinker and Persister. Channel is only one part of the puzzle: if we want communication to go through with success we need to combine a preferred channel with a favorite perception. That’s why we’ll ask different question within a conversation with a Thinker and Persister. We’ll ask:

Thinker: “What do you think…?”

Persister “What is your opinion on…? / What do you believe…?”

It is important to ask the right questions. And as much important is to know which channels are not so good to use in communication with certain types. Thinker and Persister will react really badly on others, but the worst thing you can do is to use directive channel. It will trigger them to go straight into distress, reactive aggressively form their attacker mask.

Directive Channel

Directive channel is about creating the sentence with the dot at the end of it.

I would love for all of us to demystify being direct and separate it from being aggressive, rude or too pushy.

Being directive is just saying what there’s to be done: I’m not asking you or hesitate. I just say it in a straightforward way, taking care of OK-OK perspective.

Two PCM types prefer to get it: Promoter and Imaginer. And again, it will differ on how we build a communication to each of them. That’s because their need of getting directive channel is different: Promoter doesn’t want to waste time, so they just want to get a task and move to action. Imaginer wants to be invited to share what’s in their heads, so they need direct communication to do that. So, the way we is this channel matters. We’ll say:

Promoter: “Please create this report for tomorrow, not later than 5PM.”

Imaginer: “I need this report to be done by tomorrow, not later than 5PM. Please tell me what you see in your head when I ask you to do it.”

Both are tasks we want to delegate for a person but said differently.

They are not very good at receiving requestive channel, also Imaginer will react with a drooper mask on Emotive one (too much emotion for them).

Emotive Channel

Emotive channel is about the positive energy and contact. As we can easily guess, the Rebel is our person here: it’s their favorite channel. In this one they can exchange energy, creative ideas, brainstorm and get into positive contact with others. It works even if it’s just for a little bit at the beginning of the conversation.

How can it look like?

“OH MAAAAN, this weekend was so dope, I need to tell you about it!”
“C’mon, let’s do it and then we’ll go into the agenda: it won’t kill us to talk a little bit!”

It is about 2-3 exchanges and then you can go to the point of the meeting or a conversation. Sometimes it’s just about the exchange and that’s enough: especially when you are a Rebel in a base yourself, you’ll enjoy the conversation itself if it’s led that way.

Nurturative Channel

Last but not least: Harmonizer and their preferred nurturative channel.

Nurturative channel is all about seeing a person, feeding their recognition of person need. Harmonizers needs to be seen, as an important part of a team, community or other relationship.

Sometimes it’s enough to say:

“Thank you for being here. I know that recently it’s been crazy busy and hard, so I really appreciate you finding time to talk.”

The key thing here is to give a positive, nurturing recognition of a person, making them visible and important. In the world of endless task lists, constant rush and not enough time for anything, we could all use more moments like this for a proper recognition and a gratitude that will give us more conscience that we can’t take everything and everyone we have in our work or life for granted.

The Bottom Line

This is simple, but not always easy: use the channel that your recipient prefers, not what is your preferred way to receive communication from others. It’s not a problem when on the other side of communication process is the person who prefers the same channel as we do: then we don’t need to stretch at all. The situation gets more complicated when we need to reach to our condo on the higher levels of skills: we can do it, since we all have all resources in us.

Being mindful about our own preferences and how much does it cost to reach to each of the others is the first step to train the muscle of using the right channel. I believe it’s worth it, when we think about all those hours that we waste on clarifying communication and resolving misunderstandings.

What do you say: is it worth it for you too?

PS. Here’s a great podcast around communication itself (not PCM-related, but also really insightful):

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