WEBVTT 00:00:00.000 --> 00:00:03.240 The rules have changed on getting business projects 00:00:03.240 --> 00:00:05.780 done. Dump the old timelines and requirements. 00:00:06.259 --> 00:00:10.160 Speed, implementing the latest technology along 00:00:10.160 --> 00:00:13.119 with security, are now the critical requirements. 00:00:13.919 --> 00:00:17.219 We're living in a world where the old rules just 00:00:17.219 --> 00:00:20.980 don't cut it anymore. Deadlines are tighter. 00:00:22.059 --> 00:00:25.559 Expectations are higher. And, well, let's face 00:00:25.559 --> 00:00:30.359 it, burnout is lurking around every corner. But 00:00:30.359 --> 00:00:33.600 what if there is a better way, a way to execute 00:00:33.600 --> 00:00:36.899 projects so fast and flawlessly that people won't 00:00:36.899 --> 00:00:40.439 know whether to be amazed or terrified? Hi, it's 00:00:40.439 --> 00:00:43.340 Wayne Robertson. If you're here to follow the 00:00:43.340 --> 00:00:46.079 same tired project management playbook, you're 00:00:46.079 --> 00:00:48.780 probably in the wrong place. But if you're ready 00:00:48.780 --> 00:00:51.600 to ditch the noise, smash through roadblocks, 00:00:51.619 --> 00:00:55.219 and deliver results that'll have everybody wondering 00:00:55.219 --> 00:00:58.899 how you did it, then stick around. Here on the 00:00:58.899 --> 00:01:01.899 Ignoring the Rules podcast, I'm not just talking 00:01:01.899 --> 00:01:05.079 about thinking outside the box. I'm setting the 00:01:05.079 --> 00:01:08.480 thing on fire. We want to dive deep into strategies 00:01:08.480 --> 00:01:11.340 that rip the status quo, cut through the noise, 00:01:11.400 --> 00:01:14.840 and make things happen without sacrificing your 00:01:14.840 --> 00:01:18.719 sanity or selling your soul. I want to break 00:01:18.719 --> 00:01:21.900 down real -world tactics that you can start using 00:01:21.900 --> 00:01:25.140 today. I want to arm you to redefine success 00:01:25.140 --> 00:01:28.519 by doing it your way. and I want to give you 00:01:28.519 --> 00:01:32.379 some ideas about it. So, if you're ready to challenge 00:01:32.379 --> 00:01:35.260 everything you've been told, to push limits, 00:01:35.459 --> 00:01:38.560 to redefine what's possible, then buckle up. 00:01:38.879 --> 00:01:43.000 This isn't just another business podcast. This 00:01:43.000 --> 00:01:46.260 is Ignoring the Rules, and it's time to turn 00:01:46.260 --> 00:01:49.420 the game on its head. Whether you're a project 00:01:49.420 --> 00:01:52.599 manager, upper manager, or someone who is just 00:01:52.599 --> 00:01:55.879 curious about new ways to get things done, This 00:01:55.879 --> 00:01:58.739 session is going to be packed with insights and 00:01:58.739 --> 00:02:01.640 practical tips. So get ready to break the mold, 00:02:01.819 --> 00:02:04.620 think outside the box, and discover how you can 00:02:04.620 --> 00:02:07.439 lead your team to success without burning out. 00:02:31.689 --> 00:02:34.189 If you work on projects in your organization, 00:02:34.250 --> 00:02:37.169 whether you are an executive, middle management, 00:02:37.389 --> 00:02:41.810 or at the line level, this podcast will change 00:02:41.810 --> 00:02:46.310 your perspective. By making a few changes in 00:02:46.310 --> 00:02:49.250 your work, you can make major accomplishments 00:02:49.250 --> 00:02:56.180 and successes and supercharge your project. The 00:02:56.180 --> 00:02:59.360 following story is fictional, as I need to keep 00:02:59.360 --> 00:03:02.400 the actual experience as confidential, but it 00:03:02.400 --> 00:03:05.439 illustrates key issues that arise in getting 00:03:05.439 --> 00:03:09.300 projects done. Jorge was known in his company 00:03:09.300 --> 00:03:13.099 for his technical prowess. But when his team 00:03:13.099 --> 00:03:16.400 started facing mounting pressures, missed deadlines 00:03:16.400 --> 00:03:20.569 and quality issues, It became clear that expertise 00:03:20.569 --> 00:03:24.289 alone wasn't enough. The demands of the project 00:03:24.289 --> 00:03:27.530 were leading to burnout, and work -life balance 00:03:27.530 --> 00:03:30.849 was slipping away. He saw his talented team's 00:03:30.849 --> 00:03:33.930 motivation decreasing, and he knew he had to 00:03:33.930 --> 00:03:37.629 act fast to salvage both the project and the 00:03:37.629 --> 00:03:41.810 team's morale. So, ignoring the conventional 00:03:41.810 --> 00:03:46.050 rules, Jorge took a step back. and engaged his 00:03:46.050 --> 00:03:49.569 team in open conversations to understand their 00:03:49.569 --> 00:03:52.629 challenges he listened to their concerns about 00:03:52.629 --> 00:03:56.710 workload unrealistic expectations and the impact 00:03:56.710 --> 00:04:00.189 on their personal lives and realizing that a 00:04:00.189 --> 00:04:02.930 different approach was needed he shifted his 00:04:02.930 --> 00:04:06.629 focus from pushing harder to working smarter 00:04:06.629 --> 00:04:11.610 so jorge's transformation started with a simple 00:04:11.610 --> 00:04:15.789 yet powerful shift he replaced the traditional 00:04:15.789 --> 00:04:20.069 top -down directives with an inclusive team -centric 00:04:20.069 --> 00:04:22.870 approach. And here are some of the changes that 00:04:22.870 --> 00:04:26.189 he implemented across his project, the team, 00:04:26.230 --> 00:04:31.889 and eventually the company. First of all, he 00:04:31.889 --> 00:04:34.910 redefined the project goals and priorities. He 00:04:34.910 --> 00:04:37.230 looked closely at project roadmap, found that 00:04:37.230 --> 00:04:40.430 unrealistic timelines and overloading team members 00:04:40.430 --> 00:04:42.529 were creating a cycle of missed deadlines and 00:04:42.529 --> 00:04:46.740 stress. He broke down large tasks into smaller, 00:04:46.959 --> 00:04:51.100 achievable milestones and allowed the team to 00:04:51.100 --> 00:04:53.899 celebrate small wins and maintain a steady sense 00:04:53.899 --> 00:04:57.620 of accomplishment. He also worked with his team 00:04:57.620 --> 00:05:01.180 to set achievable deadlines based on their insights 00:05:01.180 --> 00:05:04.600 and comfort levels, considering personal workloads, 00:05:04.939 --> 00:05:08.740 work -life balance, and he built in buffers for 00:05:08.740 --> 00:05:12.790 innovation, and problem solving, which were previously 00:05:12.790 --> 00:05:17.829 lacking due to constant pressure. He also introduced 00:05:17.829 --> 00:05:22.730 a task rotation system that enabled team members 00:05:22.730 --> 00:05:25.389 to work on different types of tasks, breaking 00:05:25.389 --> 00:05:28.170 the monotony and giving everyone a chance to 00:05:28.170 --> 00:05:31.250 develop diverse skills while balancing difficult 00:05:31.250 --> 00:05:35.850 and more routine tasks. Also, instead of the 00:05:35.850 --> 00:05:39.670 typical brief status updates, Jorge encouraged 00:05:39.670 --> 00:05:42.889 team members to express both work -related concerns 00:05:42.889 --> 00:05:47.029 and personal stressors. He actively listened, 00:05:47.250 --> 00:05:50.410 asking questions to understand their frustrations 00:05:50.410 --> 00:05:54.470 and challenges, and this fostered a culture where 00:05:54.470 --> 00:05:58.810 team members felt heard and valued. And after 00:05:58.810 --> 00:06:03.649 each project phase, Jorge hosted deliberate retrospective 00:06:03.649 --> 00:06:07.819 meetings, emphasizing transparency. and team 00:06:07.819 --> 00:06:10.759 members shared what went well and what didn't, 00:06:10.860 --> 00:06:15.279 without fear of judgment. He also implemented 00:06:15.279 --> 00:06:18.480 changes based on this feedback, and he made sure 00:06:18.480 --> 00:06:22.500 that everyone saw the results of their input. 00:06:23.560 --> 00:06:27.399 He also scheduled regular one -on -ones, which 00:06:27.399 --> 00:06:30.319 are really critical, where the team members could 00:06:30.319 --> 00:06:34.300 discuss not only their progress, but also any 00:06:34.300 --> 00:06:38.100 personal, or professional issues that they were 00:06:38.100 --> 00:06:41.899 facing. He connected employees with mental health 00:06:41.899 --> 00:06:45.839 resources and encouraged self -care, emphasizing 00:06:45.839 --> 00:06:48.740 that their well -being mattered as much as the 00:06:48.740 --> 00:06:52.079 project's success. He also noticed that rigid 00:06:52.079 --> 00:06:56.259 hours were a significant stressor. He introduced 00:06:56.259 --> 00:06:59.240 flexible working hours, allowing team members 00:06:59.240 --> 00:07:02.660 to set schedules that suited their personal lives. 00:07:03.600 --> 00:07:07.019 Remote work became an option for those that preferred 00:07:07.019 --> 00:07:10.180 it, acknowledging that different environments 00:07:10.180 --> 00:07:14.160 fueled different productivity levels. Understanding 00:07:14.160 --> 00:07:16.839 that technical teams needed time to upgrade skills, 00:07:17.199 --> 00:07:20.899 he introduced development days where team members 00:07:20.899 --> 00:07:24.199 could focus on learning new tools, exploring 00:07:24.199 --> 00:07:27.259 innovations or pursuing training in their areas 00:07:27.259 --> 00:07:30.259 of interest. And this not only motivated the 00:07:30.259 --> 00:07:34.100 team, It actually improved the overall project 00:07:34.100 --> 00:07:39.379 quality. And to solve a problem to ensure that 00:07:39.379 --> 00:07:42.879 team members could genuinely unwind, he enforced 00:07:42.879 --> 00:07:48.360 a strict no -work -after -hours rule. He prohibited 00:07:48.360 --> 00:07:51.680 emails and messages outside working hours because 00:07:51.680 --> 00:07:55.300 he wanted the team to recharge and prevent burnout. 00:07:55.759 --> 00:07:59.000 Jorge also encouraged team members to take ownership 00:07:59.000 --> 00:08:02.459 of individual tasks, empowering them to make 00:08:02.459 --> 00:08:07.480 decisions within their roles. This autonomy fostered 00:08:07.480 --> 00:08:10.139 a sense of pride and accountability, reduced 00:08:10.139 --> 00:08:14.279 the need for micromanagement, and boosting the 00:08:14.279 --> 00:08:18.019 team's confidence in their work. He also held 00:08:18.019 --> 00:08:20.639 bi -weekly meetings with other departments, which 00:08:20.639 --> 00:08:23.139 helped his team see how their work impacted the 00:08:23.139 --> 00:08:26.189 broader company goals. and this transparency 00:08:26.189 --> 00:08:30.709 fueled a much greater sense of purpose and collaboration 00:08:30.709 --> 00:08:34.129 and it made the team feel part of something larger 00:08:34.129 --> 00:08:39.169 jorge also introduced a reward system that celebrated 00:08:39.169 --> 00:08:42.470 personal achievements from hitting small milestones 00:08:42.470 --> 00:08:46.269 to major project completions recognitions were 00:08:46.269 --> 00:08:50.029 shared company -wide raising morale and fostering 00:08:50.029 --> 00:08:54.419 an environment of appreciation also after seeing 00:08:54.419 --> 00:08:58.980 how inefficient processes affected his team jorge 00:08:58.980 --> 00:09:01.639 proposed changes to the company -wide procedures 00:09:01.639 --> 00:09:03.840 he worked with upper management to eliminate 00:09:03.840 --> 00:09:07.019 unnecessary administrative burdens which gave 00:09:07.019 --> 00:09:09.620 team members more time to focus on their work 00:09:09.620 --> 00:09:14.320 and he initiated regular meetings with company 00:09:14.320 --> 00:09:17.840 executives where he openly shared his team's 00:09:17.840 --> 00:09:21.179 experiences and the benefits of the new practices 00:09:21.179 --> 00:09:25.399 that he had implemented seeing the positive impact 00:09:25.399 --> 00:09:28.200 management adopted some of his team -focused 00:09:28.200 --> 00:09:31.620 strategies and implemented them in other departments 00:09:31.620 --> 00:09:36.740 so impressed by the improvement in both productivity 00:09:36.740 --> 00:09:39.879 and morale the company adopted his well -being 00:09:39.879 --> 00:09:43.159 practices across the teams they launched a comprehensive 00:09:43.159 --> 00:09:45.379 program that included mental health resources 00:09:45.379 --> 00:09:49.240 flexible work policies and a continuous feedback 00:09:49.240 --> 00:09:53.059 system. So, with a team that was refreshed and 00:09:53.059 --> 00:09:57.159 motivated, Jorge saw deadlines consistently met 00:09:57.159 --> 00:10:01.059 and project quality increase, which in turn brought 00:10:01.059 --> 00:10:05.299 in new clients and more visibility for his department. 00:10:05.919 --> 00:10:09.139 And so, by prioritizing his work -life balance, 00:10:09.360 --> 00:10:14.220 Jorge's team felt valued, respected, it significantly 00:10:14.220 --> 00:10:18.480 reduced turnover, and he retained valuable talent. 00:10:18.940 --> 00:10:22.220 And employees from other teams began requesting 00:10:22.220 --> 00:10:25.419 transfers to his team, drawn to the positive, 00:10:25.559 --> 00:10:28.840 balanced environment. And Jorge's department 00:10:28.840 --> 00:10:32.080 became a model for others, showcasing the benefits 00:10:32.080 --> 00:10:35.220 of prioritizing employee well -being without 00:10:35.220 --> 00:10:40.600 sacrificing productivity, so critical. His initiatives 00:10:40.600 --> 00:10:43.539 were rolled out across the company and making 00:10:43.539 --> 00:10:47.070 him a pioneer of cultural change. It was a tough 00:10:47.070 --> 00:10:50.870 road, but he made it. Throughout this whole journey, 00:10:51.090 --> 00:10:55.169 Jorge proved that the project manager could create 00:10:55.169 --> 00:10:59.850 meaningful, lasting change by valuing people 00:10:59.850 --> 00:11:03.570 over rigid processes and demonstrating the transformative 00:11:03.570 --> 00:11:07.730 power of empathy, flexibility, and adaptability 00:11:07.730 --> 00:11:11.490 in today's demanding work environment. So what's 00:11:11.490 --> 00:11:14.509 the secret to supercharging your projects? Well... 00:11:15.480 --> 00:11:18.620 If you're in tech, caffeine, code, and a healthy 00:11:18.620 --> 00:11:21.259 disregard for sanity has been the way we always 00:11:21.259 --> 00:11:25.919 got it done. And sometimes you wonder, what is 00:11:25.919 --> 00:11:28.299 a tech project manager's favorite type of coffee? 00:11:28.639 --> 00:11:31.519 Well, the kind that keeps them awake while silently 00:11:31.519 --> 00:11:36.200 screaming inside. That is the world we live in. 00:11:36.740 --> 00:11:39.399 And you know, we've all been there. The deadline 00:11:39.399 --> 00:11:43.600 looms like a hungry monster, and the to -do list 00:11:43.600 --> 00:11:46.759 stretches to infinity. You find yourself wondering, 00:11:47.039 --> 00:11:49.960 is there a way to clone myself without violating 00:11:49.960 --> 00:11:53.929 the ethical guidelines? Well, I think we don't 00:11:53.929 --> 00:11:56.629 have to do that, because I'm here to sprinkle 00:11:56.629 --> 00:12:00.649 some time -saving ideas on your project woes. 00:12:00.750 --> 00:12:03.710 Before I break out the magic wands and the time 00:12:03.710 --> 00:12:06.429 -traveling unicorns, let's address the elephant 00:12:06.429 --> 00:12:09.730 in the room. Why are we always racing the clock 00:12:09.730 --> 00:12:13.690 anyway? It's like the universe decided to challenge 00:12:13.690 --> 00:12:16.730 us to a game of beat the deadline, but didn't 00:12:16.730 --> 00:12:21.059 tell us any rules. So buckle up, grab your favorite 00:12:21.059 --> 00:12:23.580 caffeinated beverage, and let's get ready to 00:12:23.580 --> 00:12:26.320 laugh and learn, and maybe even shed a tear or 00:12:26.320 --> 00:12:28.759 two as we get through this, because together 00:12:28.759 --> 00:12:31.179 we're going to turn those project hurdles around, 00:12:31.399 --> 00:12:34.100 and we can leap over them in a single bound. 00:12:34.399 --> 00:12:36.860 One of the things that is critical is to lead 00:12:36.860 --> 00:12:41.539 the project from behind. Now, how can projects 00:12:41.539 --> 00:12:45.200 be led from behind? Well, it started out when 00:12:45.200 --> 00:12:47.759 I flipped the normal organization pyramid on 00:12:47.759 --> 00:12:50.629 its head. and put the working team at the top. 00:12:51.049 --> 00:12:53.590 I've spent over 36 years working in technology 00:12:53.590 --> 00:12:57.629 on a wide variety of projects. The standard project 00:12:57.629 --> 00:12:59.850 leadership model shows the management at the 00:12:59.850 --> 00:13:03.409 top of the team pyramid. But when I pondered 00:13:03.409 --> 00:13:06.169 this, the most important people are those that 00:13:06.169 --> 00:13:08.769 are normally down at the bottom. These are the 00:13:08.769 --> 00:13:12.129 people doing the actual work. By flipping the 00:13:12.129 --> 00:13:14.730 pyramid, the most important team members that 00:13:14.730 --> 00:13:17.899 were doing the work are on top. My job as a project 00:13:17.899 --> 00:13:21.139 leader was to support and take care of the team 00:13:21.139 --> 00:13:23.320 members and make sure they can get the work done. 00:13:24.740 --> 00:13:28.539 So, project management and the workplace offer 00:13:28.539 --> 00:13:33.700 a rich vein of stories and humor. We like to 00:13:33.700 --> 00:13:36.399 poke fun at common pitfalls and quirky aspects. 00:13:37.320 --> 00:13:41.779 You have three phases in a project. A beginning, 00:13:41.940 --> 00:13:45.399 the muddle, and the end. There's a universal 00:13:45.399 --> 00:13:49.299 project management truth. The six phases of a 00:13:49.299 --> 00:13:52.159 project. Enthusiasm, disillusionment, panic, 00:13:52.399 --> 00:13:55.559 search for the guilty, punishment of the innocent, 00:13:55.740 --> 00:13:59.379 praise and honor for the non -participants. Been 00:13:59.379 --> 00:14:04.480 there, done that. This story is also fiction, 00:14:04.659 --> 00:14:07.500 but it illustrates the concepts of what we bump 00:14:07.500 --> 00:14:12.080 into in real life. Jake was a skilled and dedicated 00:14:12.080 --> 00:14:15.759 project manager at a tech firm, and he faced 00:14:15.759 --> 00:14:18.379 one of the toughest challenges of his career. 00:14:19.139 --> 00:14:22.360 The Eclipse project, which was an ambitious endeavor 00:14:22.360 --> 00:14:25.700 to develop a cutting -edge virtual reality platform, 00:14:25.960 --> 00:14:29.539 was in deep trouble. The project was behind schedule, 00:14:29.899 --> 00:14:34.980 it was over budget, and the team was demoralized. 00:14:35.379 --> 00:14:39.629 So this is how Jake turned things around. When 00:14:39.629 --> 00:14:42.149 he was assigned to lead the Eclipse project, 00:14:42.509 --> 00:14:45.909 he quickly realized the extent of the issues. 00:14:46.470 --> 00:14:49.889 Deadlines had been missed, features were incomplete, 00:14:50.190 --> 00:14:54.210 and the team was overworked and disheartened. 00:14:54.750 --> 00:14:57.549 So his first step was to understand the root 00:14:57.549 --> 00:15:00.769 causes of these problems, and he organized a 00:15:00.769 --> 00:15:03.169 series of one -on -one meetings, which are absolutely 00:15:03.169 --> 00:15:07.490 critical, with each team member to listen to 00:15:07.490 --> 00:15:12.250 their concerns, and frustrations and common themes 00:15:12.250 --> 00:15:17.129 emerged unclear objectives constant changes in 00:15:17.129 --> 00:15:20.370 requirements the lack of communication from the 00:15:20.370 --> 00:15:23.690 previous project manager and he took detailed 00:15:23.690 --> 00:15:28.129 notes and recognized that rebuilding trust and 00:15:28.129 --> 00:15:33.809 clarity would be crucial he also knew that for 00:15:33.809 --> 00:15:37.710 the project to succeed He needed to rebuild the 00:15:37.710 --> 00:15:40.769 team's morale and trust, and he called a team 00:15:40.769 --> 00:15:43.909 meeting and openly acknowledged the challenges 00:15:43.909 --> 00:15:47.490 they were facing, and he assured them that he 00:15:47.490 --> 00:15:50.549 was there to support them and that together they 00:15:50.549 --> 00:15:54.149 could turn things around. He introduced a new 00:15:54.149 --> 00:15:56.629 approach to project management based on transparency 00:15:56.629 --> 00:16:00.450 and collaboration, and he implemented regular 00:16:00.450 --> 00:16:04.210 team meetings where everyone could voice their 00:16:04.210 --> 00:16:08.490 opinions, and share updates, and he also created 00:16:08.490 --> 00:16:12.490 a project dashboard that clearly outlined goals 00:16:12.490 --> 00:16:16.370 and deadlines and individual responsibilities, 00:16:16.429 --> 00:16:20.590 which ensured that everyone knew what was expected 00:16:20.590 --> 00:16:24.250 and how their work contributed to the project's 00:16:24.250 --> 00:16:29.129 success. Jake understood the importance of empowering 00:16:29.129 --> 00:16:32.029 his team members and encouraged them to take 00:16:32.029 --> 00:16:35.379 ownership of their tasks. and provided them with 00:16:35.379 --> 00:16:39.559 autonomy to make the decisions he fostered a 00:16:39.559 --> 00:16:42.539 culture of continuous feedback where the team 00:16:42.539 --> 00:16:45.799 members were encouraged to share their ideas 00:16:45.799 --> 00:16:49.039 and their concerns without fear of criticism 00:16:49.039 --> 00:16:52.840 and he also recognized the team was overworked 00:16:52.840 --> 00:16:56.740 he advocated for more realistic deadlines with 00:16:56.740 --> 00:16:59.700 upper management he emphasized the long -term 00:16:59.700 --> 00:17:02.980 benefits of a well -rested and motivated team 00:17:03.529 --> 00:17:06.930 and his efforts paid off, and the revised timeline 00:17:06.930 --> 00:17:10.349 allowed the team to focus on quality without 00:17:10.349 --> 00:17:14.349 the constant pressure of looming deadlines. He 00:17:14.349 --> 00:17:17.789 also invested in the team's professional development. 00:17:17.990 --> 00:17:20.509 He organized training sessions and workshops 00:17:20.509 --> 00:17:24.410 to help them enhance their skills and stay updated 00:17:24.410 --> 00:17:28.509 on the latest virtual reality technologies. But 00:17:28.509 --> 00:17:31.349 this not only improved their performance, it 00:17:31.349 --> 00:17:34.890 actually also boosted their confidence and enthusiasm 00:17:34.890 --> 00:17:41.430 for the project and as the team regained their 00:17:41.430 --> 00:17:45.609 footing they faced several complex technical 00:17:45.609 --> 00:17:49.430 challenges which always happens so he took a 00:17:49.430 --> 00:17:52.410 hands -on approach worked alongside the developers 00:17:52.410 --> 00:17:55.829 to brainstorm solutions and troubleshoot issues 00:17:55.829 --> 00:17:59.210 and his willingness to get involved and share 00:17:59.210 --> 00:18:03.019 the workload demonstrated his commitment to the 00:18:03.019 --> 00:18:08.140 project and to the team. He also leveraged the 00:18:08.140 --> 00:18:11.160 team's collective expertise and he organized 00:18:11.160 --> 00:18:13.599 brainstorming sessions where team members could 00:18:13.599 --> 00:18:17.039 collaborate and contribute based on their unique 00:18:17.039 --> 00:18:20.500 perspectives. And this collaborative approach 00:18:20.500 --> 00:18:24.460 led to innovative solutions that addressed the 00:18:24.460 --> 00:18:27.920 technical hurdles and pushed the project forward. 00:18:29.380 --> 00:18:33.250 And something really important. Jake believed 00:18:33.250 --> 00:18:37.730 in the power of celebrating progress no matter 00:18:37.730 --> 00:18:43.509 how small. He made it a point to recognize and 00:18:43.509 --> 00:18:47.390 celebrate milestones, fostering a sense of achievement 00:18:47.390 --> 00:18:51.190 and camaraderie within the team. Now, whether 00:18:51.190 --> 00:18:53.470 it was completing a challenging feature or meeting 00:18:53.470 --> 00:18:56.529 a deadline, Jake ensured that these successes 00:18:56.529 --> 00:19:00.250 were acknowledged. He organized team lunches, 00:19:00.589 --> 00:19:03.630 informal gatherings to build a strong sense of 00:19:03.630 --> 00:19:07.190 community and these events help to strengthen 00:19:07.190 --> 00:19:10.970 relationships reduce stress and maintain a positive 00:19:10.970 --> 00:19:16.009 atmosphere so with a clear vision and an empowered 00:19:16.009 --> 00:19:19.250 team and a supportive environment from management 00:19:19.250 --> 00:19:24.759 the eclipse project began to gain momentum and 00:19:24.759 --> 00:19:27.740 the team's productivity increased they started 00:19:27.740 --> 00:19:30.960 hitting the revised milestones the quality of 00:19:30.960 --> 00:19:33.599 their work improved and the project began to 00:19:33.599 --> 00:19:37.099 take shape and jake maintained open lines of 00:19:37.099 --> 00:19:39.819 communication with upper management providing 00:19:39.819 --> 00:19:42.920 regular updates on the project's progress and 00:19:42.920 --> 00:19:46.220 his transparent approach even when there were 00:19:46.220 --> 00:19:49.940 problems and the team's visible improvement garnered 00:19:49.940 --> 00:19:52.720 support and confidence from upper management. 00:19:53.599 --> 00:19:57.619 And so as the project neared completion, the 00:19:57.619 --> 00:20:00.900 team worked cohesively to address the final challenges 00:20:00.900 --> 00:20:04.420 to polish the platform. And their dedication, 00:20:04.799 --> 00:20:08.220 their hard work paid off, and the Eclipse VR 00:20:08.220 --> 00:20:12.019 platform was completed on time, the new schedule, 00:20:12.160 --> 00:20:17.079 and the new budget. The launch of this platform 00:20:17.079 --> 00:20:19.920 was met with widespread acclaim. The innovative 00:20:19.920 --> 00:20:23.220 features and high -quality user experience impressed 00:20:23.220 --> 00:20:26.779 both the users and the industry experts. And 00:20:26.779 --> 00:20:30.039 so this project, which was once a huge failure, 00:20:30.319 --> 00:20:34.859 became a success. But at the launch celebration, 00:20:35.240 --> 00:20:38.740 and this is really important, Jake took to the 00:20:38.740 --> 00:20:42.259 stage to thank his team. he acknowledged their 00:20:42.259 --> 00:20:45.839 hard work resilience and creativity in emphasizing 00:20:45.839 --> 00:20:49.119 that their success was a collective achievement 00:20:49.119 --> 00:20:52.160 because the team's journey from disheartened 00:20:52.160 --> 00:20:55.960 and overworked to motivated and successful was 00:20:55.960 --> 00:20:59.500 a testament to the power of focusing on people 00:20:59.500 --> 00:21:03.319 first and his success in the eclipse project 00:21:03.319 --> 00:21:07.339 became a model for effective project management 00:21:07.339 --> 00:21:10.660 within the company. His approach to putting the 00:21:10.660 --> 00:21:14.880 team first, fostering a great collaborative environment, 00:21:15.059 --> 00:21:19.099 and celebrating achievements demonstrated that 00:21:19.099 --> 00:21:22.799 a project manager's most valuable asset is the 00:21:22.799 --> 00:21:26.799 team. And Jake continued to lead new projects 00:21:26.799 --> 00:21:30.259 with the same philosophy, mentoring other project 00:21:30.259 --> 00:21:34.720 managers and sharing his experiences. and his 00:21:34.720 --> 00:21:38.279 journey serves as an inspiring example of how 00:21:38.279 --> 00:21:41.420 focusing on the well -being and empowerment of 00:21:41.420 --> 00:21:44.180 team members can turn even the most troubled 00:21:44.180 --> 00:21:50.220 projects into success. So, supercharging your 00:21:50.220 --> 00:21:54.480 project work involves enhancing efficiency, productivity, 00:21:54.819 --> 00:21:58.000 and outcomes through great planning, some effective 00:21:58.000 --> 00:22:03.059 management, and the right tools. So things like 00:22:03.059 --> 00:22:05.500 defining clear objectives. I know this sounds 00:22:05.500 --> 00:22:09.380 obvious, but you would be amazed. You've got 00:22:09.380 --> 00:22:13.279 to start with a clear, concise statement of what 00:22:13.279 --> 00:22:16.680 the project aims to achieve. It's got to be very 00:22:16.680 --> 00:22:21.119 specific. It's got to be very measurable and 00:22:21.119 --> 00:22:26.299 achievable. It's got to be relevant. And time 00:22:26.299 --> 00:22:29.240 -bound goals can guide the project towards success. 00:22:30.319 --> 00:22:32.440 And so you break down the project into smaller 00:22:32.440 --> 00:22:36.420 tasks. Use any of the management methodologies 00:22:36.420 --> 00:22:39.900 like Agile or Scrum or Kanban or any of those. 00:22:39.960 --> 00:22:44.079 It's fine. This just helps in tracking progress. 00:22:45.339 --> 00:22:47.519 All of those are good. There are many more that 00:22:47.519 --> 00:22:52.700 are good too. And don't forget to utilize project 00:22:52.700 --> 00:22:55.559 management tools and software. to help with your 00:22:55.559 --> 00:22:58.039 task management and scheduling. These are kind 00:22:58.039 --> 00:23:02.180 of obvious, so I won't spend time on that. As 00:23:02.180 --> 00:23:05.779 we saw in the stories, foster a culture of open 00:23:05.779 --> 00:23:08.119 communication and teamwork. By the way, that 00:23:08.119 --> 00:23:12.900 brings up something. When you get given bad news, 00:23:13.059 --> 00:23:17.240 don't respond. Don't fall apart. Just listen, 00:23:17.359 --> 00:23:20.680 okay? We've got bad news. Things are happening. 00:23:21.000 --> 00:23:25.420 The only answer you should be giving And I finally 00:23:25.420 --> 00:23:28.220 figured this out after many years. It's okay. 00:23:28.259 --> 00:23:31.140 How do we fix this? Because one of the things 00:23:31.140 --> 00:23:33.880 that team members are afraid of is for you to 00:23:33.880 --> 00:23:38.180 jump on them and really cuss them out for a mistake 00:23:38.180 --> 00:23:41.500 or a problem. You don't want that to happen. 00:23:42.660 --> 00:23:47.200 And by having regular meetings, Using the tools 00:23:47.200 --> 00:23:50.380 to share ideas and progress and feedback. For 00:23:50.380 --> 00:23:53.039 example, Microsoft Teams comes to mind. Excellent 00:23:53.039 --> 00:23:56.599 tool for working together. You want to prioritize 00:23:56.599 --> 00:24:01.200 tasks. Those are really important. And if you 00:24:01.200 --> 00:24:03.759 want to look it up, look at the Eisenhower box. 00:24:04.319 --> 00:24:07.519 That's kind of an interesting method of doing 00:24:07.519 --> 00:24:11.569 this. Also, stay open to learning new tools and 00:24:11.569 --> 00:24:15.150 techniques and methodologies. It's easy to just 00:24:15.150 --> 00:24:17.630 get stuck on the same road you've been on forever 00:24:17.630 --> 00:24:22.410 because this field is constantly evolving and 00:24:22.410 --> 00:24:25.589 keep abreast of new developments can give you 00:24:25.589 --> 00:24:29.970 a real edge on getting things done. Identify 00:24:29.970 --> 00:24:33.710 potential risks early in the project and develop 00:24:33.710 --> 00:24:37.690 mitigation strategies. Being proactive about 00:24:37.690 --> 00:24:40.730 risk management is really important because it 00:24:40.730 --> 00:24:43.049 saves you a lot of pain later. I'll tell you 00:24:43.049 --> 00:24:47.990 that. I learned the hard way. Quality control 00:24:47.990 --> 00:24:53.329 processes. Measure, test, review, feedback loops 00:24:53.329 --> 00:24:56.970 all the time. And after completing a milestone, 00:24:57.309 --> 00:25:03.009 conduct retrospectives with the team to discuss 00:25:03.009 --> 00:25:06.799 what went well. and what could be improved, because 00:25:06.799 --> 00:25:10.440 continuous improvement is the key to supercharging 00:25:10.440 --> 00:25:14.819 future projects. By integrating these strategies, 00:25:15.039 --> 00:25:17.859 you can enhance your project's work effectiveness 00:25:17.859 --> 00:25:22.099 and leading to more successful outcomes and much 00:25:22.099 --> 00:25:26.019 greater satisfaction for both the team and management. 00:25:26.960 --> 00:25:30.660 And a critical part of getting the project done 00:25:30.660 --> 00:25:35.619 is getting the right team. I've hired many people 00:25:35.619 --> 00:25:39.819 in my career and I've had some fantastic people 00:25:39.819 --> 00:25:43.460 on projects and I've had some real problems too. 00:25:43.579 --> 00:25:47.700 It all goes both ways. And things you want to 00:25:47.700 --> 00:25:52.019 do when you're hiring a team member is you want 00:25:52.019 --> 00:25:55.359 to look for soft skills. Everyone looks at the 00:25:55.359 --> 00:25:57.920 hard skills. How well can they do their job? 00:25:58.259 --> 00:26:02.720 But their communication skills. The adaptability, 00:26:02.960 --> 00:26:06.599 the teamwork and collaboration. I will bypass 00:26:06.599 --> 00:26:10.220 a highly skilled person if they can't work within 00:26:10.220 --> 00:26:13.700 the team. It doesn't make it happen. And make 00:26:13.700 --> 00:26:16.339 sure that there's a clear understanding of each 00:26:16.339 --> 00:26:19.359 team member's roles and responsibilities. I know 00:26:19.359 --> 00:26:22.079 that sounds obvious, but you would be surprised 00:26:22.079 --> 00:26:26.380 how many times that doesn't happen. And by carefully 00:26:26.380 --> 00:26:30.390 selecting, and investing in both inexperienced 00:26:30.390 --> 00:26:35.230 and senior talent. You can build a motivated, 00:26:35.349 --> 00:26:39.369 dynamic technology team that grows together, 00:26:39.509 --> 00:26:43.049 bringing new ideas and energy to your projects. 00:26:43.950 --> 00:26:46.809 Well, that's all the time we have for this session. 00:26:46.930 --> 00:26:51.309 In the podcast, it went fast. So much to talk 00:26:51.309 --> 00:26:54.519 about. I have many more things coming up. So 00:26:54.519 --> 00:26:56.740 glad to have you along. Please go to WayneRobertson 00:26:56.740 --> 00:27:00.180 .com for the latest in new episodes, additional 00:27:00.180 --> 00:27:03.900 information about this new world of getting projects 00:27:03.900 --> 00:27:06.200 done. And you can find the different locations 00:27:06.200 --> 00:27:08.400 where you can conveniently listen to the podcast, 00:27:08.680 --> 00:27:11.920 subscribe to a mailing list, find free documents 00:27:11.920 --> 00:27:15.299 I've created, news and information about upcoming 00:27:15.299 --> 00:27:19.450 podcasts. And I also welcome comments. about 00:27:19.450 --> 00:27:22.369 these episodes and subjects you'd like to see 00:27:22.369 --> 00:27:25.349 in future episodes. I don't have all the answers. 00:27:25.549 --> 00:27:28.309 And so I'm always happy to see your comments 00:27:28.309 --> 00:27:31.910 and information. We are all in this together. 00:27:32.470 --> 00:27:35.650 And the more we share information, the better 00:27:35.650 --> 00:27:39.269 off we all will be. So let us all know what you 00:27:39.269 --> 00:27:42.269 found that works in your projects. And I look 00:27:42.269 --> 00:27:44.670 forward to getting together with you next time 00:27:44.670 --> 00:27:47.170 on Ignoring the Rules podcast.