The Leadership Journey: From Traits to Transformation
- Due No due date
- Points 5
- Questions 5
- Time Limit None
- Allowed Attempts 3
Instructions
Unit 3 The Leadership Journey: From Traits to Transformation
Instructions
Read the story about Monica Rivera and her challenge at Horizon Technologies. As you read, pay close attention to the problems she faces and how she uses different leadership ideas to fix them. Then, use the provided reflection questions to think about your own understanding of leadership.
Case Study: The Leadership Journey
Part 1: The Big Leadership Problem
Monica Rivera sat in her new office, looking at an email from the chief executive officer (CEO). She had just been made the director of operations at Horizon Technologies. Her big job was to fix the company’s product development team, which was really struggling. They had missed their goals for the last three months, morale was low, and two key team leaders had quit.
“Monica, you need to fix this,” the CEO’s email said. “Your past work shows you can do it. I believe you have what it takes to lead this team to success.”
Monica sighed. People had always called her a “natural leader”—confident, smart, quick to decide, and charming. These qualities helped her in old jobs. But this time, she felt it wasn’t just about her personal traits. The team’s problems were complex, involving both technical issues and human challenges.
Getting ready for her first team meeting, Monica thought about her leadership classes. She’d studied many leadership ideas (theories) that had changed over time. Maybe understanding these ideas could help her create a better plan. She knew she needed more than just being “naturally confident” to turn things around.
Part 2: How Ideas About Leadership Changed Over Time
Monica opened her old leadership textbook. She started reviewing the main ideas about leadership:
Monica closed her textbook. She now had a rich toolkit. She knew she had to use the right tool for the right problem and the right person.
Part 3: Using Ideas to Fix Things
The next morning, Monica came to the office early to observe the team. She saw:
- Senior engineers worked alone: They didn’t talk much with newer team members.
- Marketing was frustrated: They felt engineers didn’t understand customer needs.
- Junior members were quiet: They seemed scared to share ideas.
- Everyone needed something different.
During the meeting, Monica introduced herself and asked everyone to share their problems. People were careful at first. But Monica used active listening: she really focused, nodded, and asked thoughtful questions. Slowly, people opened up.
“The old director just told us what to do without understanding our technical problems,” said Dean, a senior engineer.
“We never get clear instructions on what’s most important,” added Sophia from marketing. “Everything is urgent, so nothing gets done well.”
“I have ideas for improving our processes,” said Jamal, a junior developer, “but no one seems interested in hearing them.”
Monica realized different team members had different needs. Senior engineers needed independence. Marketing needed better communication. Junior members needed encouragement.
Over the next six months, Monica used many leadership approaches:
- Clear expectations (task-oriented behavior): She set very clear goals and ways to measure success. For example, specific targets like “Complete user login module by March 15.”
- Teamwork (relationship-oriented behavior): She created cross-functional teams with engineers and marketers working together from the start. She encouraged team lunches to build connections.
- Changing style for each person (Situational Leadership):
- For new juniors like Jamal (low skills, high eagerness), she used a Directing (S1) style, giving step-by-step instructions.
- For struggling mid-level developers (some skill, losing motivation), she used Coaching (S2), guiding them and offering encouragement.
- For experienced but hesitant team members like Sophia (skilled, but lacking confidence), she used Supporting (S3), involving them in decisions and building their confidence.
- For senior engineers like Dean (highly skilled and confident), she used Delegating (S4), giving them big goals and letting them figure out the best way to achieve them.
- Inspiring a big vision (Transformational Leadership): She painted an exciting picture of the division’s future: “Imagine us, the leaders in innovative software ... where our products truly delight customers.” She connected daily work to this vision.
- Being real and open (Authentic Leadership): She admitted her own limits (“I’m not a coding expert”) and asked for input, which built trust.
- Removing roadblocks (Servant Leadership): She fought for more budget, simplified old processes, and helped solve team conflicts, making the team’s work easier.
By the end of the year, the division had not just stopped failing; they had exceeded their goals for the first time in 18 months! Team morale was much better, and fewer people were quitting.
In her year-end review, Monica thought about her journey. “I used to think leadership was about having the right traits or using one method. Now I understand it’s about combining many ideas and changing to fit people and situations. The theories gave me a guide, but the real learning came from using them carefully.”
The CEO smiled. “That’s why I chose you, Monica. Not just for your traits or skills, but because you learn and adapt. That’s what great leadership is.”
Select Next to Continue