“With Kapable, I learned to pause, reduce unnecessary explanations, and focus on making people understand.”

I have spent the last several years working as a firmware engineer in Apple’s modem division, where my work is highly technical. I work on transmission systems and collaborate with multiple teams to solve complex engineering problems. Being technically strong has always been an important part of my role.
But as I progressed in my career, I began to understand that technical expertise alone would not be enough for the responsibilities I wanted to take on.
The complexity of my work often means that an idea needs to be understood by several teams before it can become reality. I may understand a design, but if I cannot explain the reasoning behind it clearly, get people aligned and bring them along with the idea, the quality of the solution does not matter as much.
That was where I realised I needed to work on my communication.
Before Kapable, I had a tendency to speak continuously when explaining something. I would move from one point to another, realise I had missed something, go back, add more context and sometimes end up repeating myself. I also tended to focus heavily on the logical side of an explanation.
I knew what I wanted to say, but I was not always thinking enough about how the other person was receiving it.
Kapable made me much more conscious of that distinction.
One of the first changes I started working on was my pace. Earlier, I would think about the next sentence while still delivering the current one. I was focused on getting the information out. Now, I consciously pause so the other person has time to process what I have said.
I have also become much more structured in the way I communicate. Instead of repeatedly revisiting points, I try to organise my thoughts beforehand and make sure each part of my explanation has a purpose. I have become more comfortable giving the right amount of context and allowing the other person to ask questions rather than assuming I need to explain everything upfront.
Another important shift has been engagement. I have started using examples and relatable situations to make technical ideas easier to connect with. I also pay more attention to whether the other person is following me, rather than simply completing my explanation.
The change has also influenced how I think about leadership.
Earlier, I associated leadership largely with being technically strong and making good decisions. Today, I see that leadership also involves understanding people, handling different perspectives, managing emotions and helping a team work effectively. As I prepare for the possibility of taking on greater responsibility, I know these skills will become increasingly important.
What I value most is that the change has become visible even in spontaneous situations. During my final session, I consciously noticed myself using pauses, reducing unnecessary explanation, bringing in examples and creating more engagement.
I still have things to practise, but I now know what I am working on and why it matters.
For me, that is one of the biggest outcomes of the Kapable journey is becoming more aware of how I communicate and learning to make small, deliberate changes that create a bigger impact.