Week in Review

This Week

This week, we really dug into some big ideas. We explored how leaders make huge impacts, often behind the scenes. We started by looking at how Tim Cook orchestrated Apple's supply chain. This was about seeing the power of systems thinking and scale. We then moved to Dame Stephanie Shirley, a remarkable figure who taught us about the courage it takes to build your own voice, even when you feel you need to hide it. We spent time with Janet Yellen, understanding the clarity and conviction required for executive presence and tough boardroom judgments. Her story reminded us about making critical decisions when the stakes are incredibly high. We also honored Seymour Cray's incredible technical depth and craft, marveling at how he pushed the boundaries of what was thought possible in computation. And we heard about Gordon Bell, facing the challenge of public speaking and articulating a complex future that few could grasp. Each story, each lesson, offered a different lens on what it means to lead, to create, and to communicate effectively. This wasn't just about listening; it was about noticing the threads that connect these diverse skills to your own work and aspirations. This week's aim was to provide a framework for seeing these skills in action and considering how they might apply in your world.

Check In — for each theme covered this week

Now, let's move into our first self-check. This is where we pause. We reflect on the past few days. It's not about judgment. It is about awareness. It is about noticing what happened.

Tim Cook: The Invisible Architect of Apple's Scale (Systems & Scale Thinking)

We began the week by dissecting the operational genius of Tim Cook. His story wasn't just about Apple's bottom line. It was about seeing the invisible structures that enable massive success. We talked about how he built a global supply chain. This was a masterpiece of logistics. It wasn't flashy work, but it was fundamental. Think about the layers of complexity involved. There was sourcing materials. There was manufacturing components. There was assembly, and then distribution. All of this spanned across continents. Cook understood that scale isn't just about making more of something. It's about building resilient, efficient systems. These systems must be able to adapt and grow. We learned that true mastery often lies in the architecture. It's in the underlying processes that ensure smooth operation. This holds true even when demand skyrockets or unexpected disruptions hit.

This isn't just for global tech giants. Every project you undertake, every team you manage, every personal goal you pursue—it all has its own system. How you design that system, how you think about its inputs, its processes, and its outputs, dictates its potential for scale and its resilience. His approach teaches us to look beyond the immediate task. It pushes us to consider the entire ecosystem surrounding what we do. Where are the bottlenecks? Where can we introduce leverage? What assumptions are we making about efficiency or growth? It's about thinking several steps ahead. It is not just reacting to what's in front of you. This involves anticipating problems. It means optimizing workflows. It means creating redundancies where necessary. It's the difference between a one-off success and repeatable, sustainable achievement. It is about building something that can endure. So, with Tim Cook's dedication to robust, scalable systems in mind, let's pause and reflect on your own week.

When you think about the idea of systems and scale, applying it to your own work or even your personal life, here are some questions to consider. Did you look at a task, a project, or even a routine this week and try to see its underlying system? Did you attempt to optimize a process, even a small one, rather than just completing the task as usual?

1. Did you attempt the action? (yes / partially / no)
   • Think about how you approached something routine this week. Did you try to map out its steps? Did you look for a way to make it more efficient for the next time, or for others who might follow?
2. What actually happened when you tried it?
   • Did you notice a change? Maybe it was small, like saving a few minutes. Or perhaps you identified a bigger problem you hadn't seen before. Describe the outcome, however minor or significant it felt.
3. What got easier, or what's still hard?
   • Did you find that by thinking systematically, some part of your work felt less chaotic? Or did you struggle to even identify the 'system' in what you do, finding it hard to pull back and see the bigger picture clearly?

Moving from the architecture of systems, let's talk about the architecture of self.

Dame Stephanie Shirley: The Voice Behind "Steve" (Building Your Voice)

Next, we turned our attention to the remarkable Dame Stephanie Shirley. Her story was a powerful lesson in building your voice. It showed us that sometimes, finding your voice means finding unconventional ways to express yourself. She operated in a male-dominated industry. She faced countless biases. She literally used the name "Steve" to get her foot in doors. Yet, through all of this, she built a company. She built a culture. This culture was founded on trust and on an unwavering commitment to her values. Her journey highlights the courage required to be authentic. It shows the resilience needed to push against expectations. She didn't just speak her mind. She built a platform where her values could speak for themselves. She created an environment where other women could thrive.

Building your voice isn't always about being the loudest person in the room. It is often about clarity. It is about conviction. It is about finding the right medium. It is about finding the right timing. It means understanding your message. It means understanding your audience. And it means having the courage to deliver that message authentically. It might mean speaking up in a meeting. It might mean writing a clear email. It might mean standing firm on a principle. Or it might mean, like Dame Stephanie, crafting a persona or a strategy that allows your true message to be heard, even when the world isn't quite ready for it. Her story asks us to consider: how do we express who we are? How do we express what we believe? How do we do this effectively, especially when circumstances are challenging? It is about making sure your ideas and your perspective don't get lost. It is about ensuring they have the impact they deserve. Think about your own week. How did you choose to express yourself?

Consider moments this week when you had an idea, a perspective, or a conviction you needed to share. Did you find a way to make it heard? Did you embrace your unique style, even if it felt a little different from the norm?

1. Did you attempt the action? (yes / partially / no)
   • Think about a specific instance where you needed to communicate something important. Did you consciously try to express your own unique perspective or conviction? Did you choose a specific approach for doing so?
2. What actually happened when you tried it?
   • Did people respond as you expected? Did you feel a sense of empowerment or vulnerability? Describe the immediate outcome of your attempt to use your voice.
3. What got easier, or what's still hard?
   • Did you find it easier to articulate your thoughts this week? Or did you encounter resistance, either from others or from within yourself, making it difficult to fully express what you intended?

Shifting our focus from finding your voice to using it with conviction in high-stakes situations.

Janet Yellen: The First Hike (Executive Presence & Boardroom Judgment)

Our journey through the week led us to Janet Yellen. She navigated immense pressure during a critical moment: the decision to raise interest rates in 2015. Her story taught us about executive presence. It showed us what boardroom judgment truly means. It was about more than just making the right call. It was about how she made that call. It was about how she communicated it. It was about how she stood firm. All of this happened in the face of intense scrutiny. Her clarity in chaos built conviction. She didn't waffle. She didn't hide. She presented her reasoning with calm authority. This reassured markets and stakeholders alike.

Executive presence isn't about charisma alone. It is about projecting confidence. It is about projecting competence. It is about projecting integrity. It means being able to distill complex information into clear, actionable insights. It means making tough decisions. It means owning those decisions. It means communicating them with a steadfast resolve. It is about showing up. It is about being fully present. It is about demonstrating that you are in control, even when the environment around you feels unpredictable. It means having the judgment to weigh all factors. It means having the courage to commit to a path. And it means possessing the presence to inspire trust, even among those who might disagree with your choice. This applies whether you're leading a company, managing a project, or even making a significant decision in your personal life. How did you handle moments this week where clear judgment and a steady presence were required? Where did you need to show up with conviction?

Think about any situations this week where you faced a significant decision, had to communicate something difficult, or needed to project confidence and clarity to others. Did you approach it with conviction?

1. Did you attempt the action? (yes / partially / no)
   • Did you have a moment where you consciously tried to exhibit executive presence or make a high-stakes judgment call? Perhaps it was a difficult conversation or a strategic choice.
2. What actually happened when you tried it?
   • How did others react to your presence or your decision? Did you feel a sense of calm authority, or did you find yourself wavering? Describe the immediate impact of your actions.
3. What got easier, or what's still hard?
   • Did you find it easier to maintain your composure or articulate your reasoning under pressure this week? Or did you still struggle with the weight of difficult decisions or with commanding attention effectively?

From the quiet power of boardroom judgment, let's explore the quiet power of deep craft.

Seymour Cray: The Unseen Architect of Speed (Technical Depth & Craft)

Then we journeyed into the world of Seymour Cray. He was the unseen architect of speed. His story was a deep dive into technical depth and craft. Cray was not just building computers. He was pushing the very boundaries of what was thought possible in computation. He had an obsessive dedication to mastering the bedrock of his field. He focused on meticulous detail. He pursued innovation that seemed almost magical at the time. His work wasn't about quick wins. It was about profound understanding. It was about elegant design. It was about unwavering quality. He built machines that redefined an industry, not by following trends, but by setting new standards of excellence through sheer technical mastery.

Technical depth and craft are about more than just knowing a lot. It is about a profound understanding of your domain. It is about the ability to innovate from first principles. It is about taking pride in the quality of your work. It is about the relentless pursuit of improvement. It means sweating the small stuff. It means understanding the 'why' behind every component, every line of code, every brushstroke, every sentence. It is the commitment to not just deliver a solution, but to deliver the best possible solution. This kind of dedication allows you to see possibilities others miss. It allows you to solve problems others deem unsolvable. It also allows you to earn respect through the undeniable quality of what you produce. Think about your own craft this week. Where did you go deeper? Where did you apply meticulous care? Did you spend extra time on something to make it truly excellent, beyond what was merely required?

Consider any tasks or projects this week where your technical skills or your craft were central. Did you consciously try to go deeper, to refine something, or to achieve a higher level of mastery?

1. Did you attempt the action? (yes / partially / no)
   • Did you dedicate extra time to understanding a technical concept? Did you meticulously refine a piece of work, even if it wasn't strictly necessary? Did you intentionally push your own standard of quality?
2. What actually happened when you tried it?
   • Did you discover new insights? Did the final product feel more robust or elegant? Describe any changes in your understanding or the quality of your output.
3. What got easier, or what's still hard?
   • Did you find that this deeper dive made future related tasks feel more manageable? Or did you struggle with the time commitment, the complexity, or the sheer effort required to achieve that level of depth?

Now, let's take all that deep craft and see how it translates to outward communication and inspiring others.

Gordon Bell: Architecting DEC's Future (Public Speaking & Presence)

Finally, we explored the story of Gordon Bell. He faced the immense challenge of public speaking and effectively selling DEC's vision for the VAX computer. He had to articulate a complex future that few could grasp. He started by convincing his own company. His challenge wasn't just about presenting facts. It was about conveying a strategic direction. It was about inspiring belief. It was about building consensus for a product that would define an era. This required more than just data. It demanded clarity, conviction, and a powerful presence. He made the intricate understandable. He made the abstract tangible. He made the future seem not just possible, but inevitable.

Public speaking and presence are about connecting. It's about taking complex ideas and making them accessible. It's about convincing. It's about persuading your audience, whether that audience is one person or a thousand. It means understanding their perspective. It means speaking to their needs. It means inspiring them to see your vision. This skill isn't confined to grand stages. It plays out in team meetings. It happens in client presentations. It happens in informal conversations where you need to get your point across. It's about choosing your words carefully. It's about structuring your message logically. It's about delivering it with confidence and passion. It means leaving your audience with a clear understanding and a sense of shared purpose. Think back through your week. Were there moments where you had to simplify a complex idea? Did you have to present a vision? Did you try to persuade someone to see things your way?

Consider any moments this week where you had to present an idea, explain a complex topic, or convince someone of a particular viewpoint. How did you prepare? How did you deliver your message?

1. Did you attempt the action? (yes / partially / no)
   • Did you consciously apply principles of good public speaking or persuasive communication? Perhaps you prepared more thoroughly for a meeting or practiced how you would explain a difficult concept.
2. What actually happened when you tried it?
   • How did your audience respond? Did they grasp your message quickly? Were they convinced? Describe the immediate reaction or outcome of your communication effort.
3. What got easier, or what's still hard?
   • Did you find that structuring your thoughts or speaking clearly felt more natural this week? Or did you still find it challenging to simplify complex information or to engage your audience effectively?

As you reflect on these individual areas, remember this isn't about perfection. It is about observation.

What's Actually Improving

Look for the small shifts in your answers above. Notice any pattern where you partially attempted something, or where something felt a little less difficult than before.

Next Week

Next week, we will explore themes of strategic vision and resilient leadership, focusing on how to foresee future challenges and build lasting impact.

This is a self-check, not a scored assessment. There is no fabricated progress metric here — only what you notice for yourself.