Showing posts with label project management. Show all posts
Showing posts with label project management. Show all posts

Friday, August 3, 2012

Musings, Cliches, Golden Nuggets From My First Consulting Engagement

I have officially closed out my first consulting engagement and although it ended sooner that I would have liked it was an amazingly rewarding learning experience that I am incredibly grateful for. My post Air Force life has been blast that has brought an incredible amount of change, enjoyment, and stress in short period of time. New hometown, new careers for the wife and I, new house, new & old friends, and a new baby girl! To add to the plethora of change in my life, I have settled into the consulting career field which essentially means that I am changing jobs within a job every few months to a year. Amidst the chaos, I really wanted to carve out some time to capture thoughts and lessons learned from my first consulting engagement at Nike. My learnings range from fairly tactical and borderline anecdotal to strategic and transcendent but I wanted them recorded nonetheless. Here they are:

- The Importance of Visually Expressing Ideas: One thing that I took away from working within Nike was the power of visually expressing ideas. The world moves fast and it is only moving faster by the day. People within successful organizations have a lot on their plate, their time is limited, and their attention spans are understandably short. Couple that with a corporate culture like that of a Nike and you have very little time to express, sell, and execute complex ideas. It was no wonder that given that context, everything....and I mean everything was done via slide decks. PowerPoint or bust. There were no long word document proposals. 

At first I found it a bit odd, especially having come from the Government contracting world where stacks of files literally consumed real estate within every organization. But over time I found it to be an incredibly liberating culture to operate within. No formal formats. Just the visual medium necessary to express an idea. What was great was that these presentations were consistently reused and/or distributed to new people to proliferate buy in as well. There wasn't any proposal or commitment document that was shelved or lost, just presentations that marked points of agreement in time amongst relevant stakeholders. An oddly relaxed yet effectively self organizing methodology that delivered results. At the end of the day shared understanding equals shared goals and objectives, so moving forward I will definitely utilize presentations as my medium of choice. 

- The Power of Facilitating Workshops/Meetings with Clearly Defined Objectives: The project I worked on had an incredibly complex network of internal and external stakeholders that needed to be aligned on where the project was headed. At times it felt like we were doing an incredible amount of work without actually accomplishing much from an enterprise perspective. It felt like swimming in place. Then all of a sudden we would have a week or two where as a project team we really moved the dial on achieving our goals. Our progress looked like a set of continuing (extremely steep) peaks and (longer) valleys. As I neared the end of my engagement I began to piece together a pattern surrounding the causes of those steep peaks of productivity. The common denominator was that we held multi day workshops with extremely defined objectives for each session, day, and workshop.

We started each workshop with a vision of what needed to be accomplished at the highest level. Ex. develop a communications strategy. Then we would break the days into sub goals to support the overarching objective. Ex. Day 1: Align on Current State of Project, Day 2: Identify Risks, Day 3: Design the Strategy, Day 4: Create the Plan. From those subcategories you could design exercises and discussions for each hour. It was a lot of work but that pattern paid extremely large dividends for a few reasons.

First and foremost, is the undeniable fact that we are social creatures. People love to come together. People really love to come together to create. When you have a complex set of stakeholders separated by function, geography, interests, etc. it becomes very easy for people to be confused, disengaged, or even become a detractor from the mission at hand. When you bring people together participate in a workshop you establish a shared understanding and more importantly you co-create a solution. It becomes a lot more difficult to pull back or sabotage a solution that you helped to created. Additionally, these workshops serve as points in time that can be signed off on by leadership. Outbriefs out of these sessions became the proposal to the powers that be. I saw time and again the fears of leadership being eased merely by the fact that they knew the right brainpower was in the room and that the due diligence behind the thinking had been performed. The workshops were the vehicle for that thinking. Lastly, highly functional teams produce great work. Nothing brings a team together like a structured workshop that allows for all concerns and perspectives to be heard without derailing the goals at hand. These workshops helped to craft a tight knit team as opposed to a group of people that happen to work on a project together.

- Bring In Other People, Meet for Coffee, Ask for Expertise: Organizations don't possess knowledge. People do. In the consulting field you are brought in for one reason....there is a problem and work to be done to solve that problem. Given that maxim, it follows that as a consultant you will constantly be thrown into situations wrought with ambiguity and complexity. Not a very comfortable feeling, especially when you first land at a new gig (as I am experiencing with client #2). What I have found to work better than anything else to get oriented in these situations is to ask someone in the organization to grab coffee. Everyone loves to help someone else. Everyone loves to be the expert. So make those around you the expert, build relationships, and reap the rewards. 

- Align with the Client on the Purpose of Meetings In Advance to Better Facilitate, Provide Consultation, Capture Key Decisions & Actions, Properly Structure Visual Frameworks: This is way more tactical in focus as compared to some of the other insights I have listed but it is important nonetheless. I have noticed that in order to provide the best support possible I need to be clearly aligned with the project sponsor on the details of a meeting prior to it occurring. This sounds really intuitive, but I am not just talking about knowing the purpose of a meeting and having an agenda. I am talking about deeper discussions that can be tedious if you have a lot of meetings but also can make so much better use of your time in the long run. Below are some example questions:

1. What are you trying to get out of this meeting?
2. Who is in the meeting and from what angle will they be coming at this meeting from (challenging, aligned, clueless, etc)?
3. Beyond the agenda, how do you see this meeting playing out?
4. How do you see me supporting? Is there a need for any facilitation? 

From those questions, I can generally brainstorm ways to support the goals of the sponsor and make recommendations for facilitation based on things that have worked in the past. If you don't do this in advance it is a struggle just to capture action items and decisions let alone have the head space to design visual brainstorming frameworks on the fly. As intuitive as this learning may seem, the challenge is consistently doing it!

- Find Mentors in Every Organization: As a consultant you don't need a mentor in the career/professional sense within the organization you supporting but that doesn't mean you don't need to seek out mentors at all. There is always someone smarter than you, more experienced than you, and downright more capable than you especially when viewed through various contextual lenses. So treat that reality as the value proposition behind seeking out mentors in everyone organization that you are a part of. Continue to be a life long learner!

- Think Strategically and Work Your Way Down to Execution: This little nugget was definitely not learned on the job in the consulting field. It was learned through a combination of education and practical experience in my military career. However, the importance of systemic thinking was reaffirmed while working on my last project. Especially in consulting, it is so easy to get stovepiped into the mind space of the task at hand. However, starting to tackle a problem at that level leads to decisions and solutions that are made in a vacuum. I have blogged recently about the power of context and the systemic challenges we often face while working through complicated problems. Those concepts dovetail nicely with the point I am making here. To effectively solve problems you need to gather a broader context of the world you are operating within. From that foundation you can begin to develop strategies that decrescendo down into more tactical level actions. By consistently pulling myself up to a high level of thinking at the front end of scoping a problem I find that I am crafting more thoughtful, inclusive, and systemic solutions.

- Beg, Borrow, & Steal....Brilliance is Borrowed: I admit that I (fittingly) stole this gem from an audiobook that I listened to recently called "Borrowing Brilliance."  Basically the premise of the book is that there are no truly original ideas. Brilliant ideas are a collection pre-existing ideas that are either expanded upon, utilized in another context, or both. It seems oddly cynical but when you walk through the logic it makes sense. I have written on the similar topic of pattern recognition in the past.

In the consulting world this is definitely a reality. There are so many frameworks and methodologies out there that have been used. Merely applying previously utilized frameworks to new scenarios can yield huge benefits.

Beyond using templates and frameworks you can beg, borrow, and steal from peers. This ties in a bit to my point above on asking for expertise, but the reality is that no problem or challenge is solved in a vacuum. The more brainpower you can garner from other people the better. Sometimes brilliance can merely be aggregating the brainpower and works of others to solve a specific problem. Although there is nothing inherently "brilliant" about gathering the brilliance of others it will be viewed as such when a solution is delivered and progress is made.

- Develop PM Solutions to the Minimum Fidelity Necessary to Execute: Project Management tools and principles are a means to an end. They are not an end in and of themselves. In most organizations project management makes people's heads explode. Nike was definitely no different. Given their corporate culture, I always had to find the very fine line between introducing process,structure, and rigor to the project while minimizing additional work for the team, respecting the corporate culture, and allowing innovative thinking to thrive. It was a challenge but it reinforced within me the understanding that as a consultant you are an enabler. You make others better. If your tools and practices aren't contributing to that maxim then you either aren't using the right tools or they are just too robust given the scenario. PMP certification holders everywhere are furious.....

- Character Always Has, Does, and Always Will Matter:  A project is only as good as the person/team behind it. Period. I have been lucky enough to be a part of some amazing teams in my life whether it be family, sports, business, or military service. Every time I am a part of a team with sound character and capable individuals I am always amazed at the results. It is like a lesson that it re-learned every time you are privileged to experience it. Be character and build character teams.

Saturday, January 14, 2012

Sustainability & The Military: Parallels Between Two Worlds

Since my departure from the Air Force I have had to try and explain to family, friends, and acquaintances what exactly it is that I am doing now. When I explain that I took a role within a start up Portland-based consulting firm called The Gunter Group people can generally follow along. However, when I get into the details of the client and division I work in I often lose people. 

I was lucky enough to have Nike as my first client in the consulting arena. It is a company that I have an immense amount of respect for not only due to the fact they are a leader in the athletic apparel arena, but because that have been a shining star company that continually innovates over time. Of course there is a coolness factor that is associated with Nike, it's products, and it's marketing and at the risk of sounding cliche' that attitude transcends throughout the World Headquarters campus. But it is the innovation piece that I am more closely aligned with in my current role and that is the part of my Nike experience that I find most engaging. It has been a great experience and I really have enjoyed my time at Nike so far.

Not only was I lucky to get Nike as a client but I was also lucky to get on within a unique division of Nike. I work in the Sustainable Business & Innovation (SB&I) division of Nike which in in its simplest form is a bit like a 'green incubator' for Nike. SB&I seeks to innovate and integrate enterprise level sustainability solutions into the Nike business model while mobilizing key external stakeholders to make industry change.

The first question I usually get is, "what do you consult?" The answer is pretty straightforward in that I provide project management support within SB&I. In short, I help to get things done. Execution.

The second question I almost always get is, "what the hell do you know about sustainability?" To be quite honest, when I started I doubt I knew much more than the average college educated Gen Y-er does about sustainability. I had a basic understanding of the concepts surrounding sustainability that were mostly garnered through osmosis in a variety life experiences. That understanding wasn't very deep and it came accompanied with limited context. 

However, having been a part of the division for the better part of four months I may have sold myself short a bit regarding what I knew about sustainability. Although I wasn't formally educated in sustainability concepts and I most certainly had never served in a role within that context before, I came from a background that shares a surprisingly large number of parallels with the sustainability world.....the military. What do sustainability and the military environments have in common?

Systemic Challenges - One thing that I learned in the military is how to operate in challenging and ambiguous environments. Throughout my career and most notably while serving in Iraq, I encountered challenges that did not have a textbook answer. There was not a clear cut best solution...or a solution at all for that matter. There were too many unknowns, too many interests, too many interconnected subsets, and too little time to easily solve problems. In the military you are forced to confront challenges that are spread and interwoven throughout a complex system. In my relatively short stint in the sustainability realm I see the same type of systemic challenges represented. 

Execution - I have discussed on BadskiBlog before that execution is everything. I am, admittedly, probably more of an idea guy by nature. I am energized by strategic thinking and collaborative brainstorming. However, I crafted my ability to get things done in the military and that is something I will always be grateful for. Now I am, in essence, getting paid for my ability to get things done and to serve as a catalyst to help other people get things done. It is a challenge and I am constantly learning but it is exciting and fulfilling as well. A military force that can rapidly work it's way through the planning/decision cycle and execute will have a competitive advantage and will overcome resource constraints to defeat its enemies over time. My sense is that companies will benefit from a similar (albeit less combative) approach to sustainability. Taking sustainability from idea to execution faster that your competitors will become a critical competitive advantage over time.

Leading Change - As an officer in the Air Force I have sat through a few leadership presentations in my day. In fact, my undergrad experience at the Air Force Academy was almost entirely centered around character based leadership. In hindsight, a great number of those sessions drifted into discussions about leading change. The military isn't all about following orders as many like to think. And although as whole the military machine may be categorized as a bludgeoning bureaucracy of sorts, in smaller pockets the most successful units/organizations are all about leading and implementing change. SB&I is all about leading change and I imagine that is consistent throughout the sustainability space. There are a ton of methodologies for leading change (a book review on John Kotter's "The Heart of Change" coming soon) but like anything else academia can only get you so far. It is the organization that can consistently lead change that will prevail in their efforts to implement sustainability or any other initiative for that matter.

Below is a video of Nike's VP of Sustainable Business & Innovation, Hannah Jones, in which she not only provides an excellent overview of what SB&I is all about, but also some of the concepts I discussed above. Definitely do yourself a favor and watch the full video and enjoy Hannah's, very eloquent, discussion on the future of sustainability.


Check out the full video HERE, it is very interesting.

Saturday, December 31, 2011

Book Review: Creative Project Management


Creative Project Management by Michael Dobson was the latest book I plucked from the local library. It was in a similar vein to my last read in that it was all about project management and given my recent career change this should surprise no one.

The book was a solid read and although it took me quite a while to make my way through it, I think that was more attributed to buying and remodeling a home than to the quality of the read. What I really liked about the book was the manner in which it illustrated fairly classic project management concepts. Instead of focusing on a few illustrations and concept diagrams, the book focused on well known (often military) leaders and how they successfully and unsuccessfully implemented project management throughout history. These historical events, viewed through a project management lens, did a lot to show how these concepts can be applied universally to projects instead of sticking with more generic examples of project management like IT implementations.

What I didn't necessarily love about the book was the way in which it dragged out relatively straight forward concepts. It wasn't that the length was the issue it was the fact that some of the concepts went into great storytelling depth with relatively little practical explanation. It almost felt like the second half of the book was filler to get the book to a certain length. Yet, taken in totality the book was a pretty solid.

Throughout the book there were great questions that every project manager should ask themselves and others regarding the project. The author even went so far as to compile these questions as an appendix at the end of the book. These questions are an extremely helpful guide in determining what elements of the project must be developed and at what stage they should be developed in order for the project to be successful. I enjoyed the way the author built the appendix so much that I copied the pages and plan on using them to help develop each stage of the projects that I manage. If anything, the book is worth picking up for that reason alone.

Notes:

Chapter 1 - Why Do 70% of Projects Fail:
- 32% of projects were delivered on time, on budget, and with the required features and functions
- 44% were finished either late, over budget, or only partially completed
- 24% failed altogether, and they were cancelled or abandoned
- Two reasons projects fail: 1. Things that nobody thought of or prepared for 2. Things everybody thought of but no one prepared for
- Four PM questions: 1. Why are we doing this? (Business Case) 2. Who has an interest & what do they want/need? (Human Being Aspect) 3. What do we have to do & how? (Project Management, Planning, Qualitative) 4. Who needs to be involved & in what way? (Top Management & Other Involvement)
- Embrace the uncertainty & fluidity of the projects you manage
- What makes this project hard? (chart pg 13) 1. Constraints - How tight are time, cost, performance? 2. Complexity - Tasks, resources, technology 3. Certainty - How much do we know about risks & issues?
- Risk = Probability X Impact
- Cognitive biases pg 18
- When work is temporary & unique the unique part guarantees the presence of uncertainty
- 2 ways of learning: 1. Have an experience and learn from it 2. Learn from someone else's experience (The second it cheaper!)

Chapter 2 - What We Know & What We Think:
- PMs are supposed to challenge assumptions whenever possible but we all have blind spots, biases, & perceptual errors that keep us from recognizing our own misjudgments
- Johari's Window test pg 28
- More PM questions: 1. What aren't we seeing correctly or at all? 2. How will people react to this project? 3. What if I'm wrong? 4. What am I not seeing?
- Ignaz Semmelweis hand washing theory pg 31
- Vietnam quote "Anybody who thinks he knows what's going on clearly doesn't understand the situation."
- Sewell Avery & General Patton project management stories
- "The fact that some geniuses were laughed at does not imply that all who are laughed at are geniuses. They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown" - Carl Sagan

Chapter 3 - The Most Dangerous Word is a Premature Yes:
- "Plans are worthless, but planning is everything. There is a very great distinction because when you are planning for an emergency you must start with this one thing: the very definition of "emergency" is that it is unexpected; therefore it is not going to happen the way you are planning." - President Dwight D. Eisenhower, speech to the National Defense Executive Reserve Conference, Washington DC 1957
- First there is a mountain, then there is no mountain, then there is a mountain." Your first understanding of the mountain is an outline, a shape in the horizon. As you get closer the mountain decomposes into a million individual details. Finally you know the mountain as a whole. Zen koan.
- No one starts a war - or rather, no on in his senses ought to do so - without being first clear in his mind what he intends to achieve by that war and how he intends to conduct it." - Clausewitz
- A project isn't the end its the means to bridge the gap
- The first step in any project is to define the gap
- Eisenhower closing the gap story pg 55
- What is the minimum that can be done now?
- Project triage: 1. Likely to survive no matter what 2. Likely to fail no matter what 3. Projects where the level of effort will make a positive impact in success

Chapter 4 - Good Enough, Barely Adequate, Failure:
- 7 Levels of project outcomes: 1. Perfect 2. Outstanding 3. Exceeds Expectations 4. Fully Satisfactory 5. Barely Adequate 6. Failure 7. Catastrophe

Chapter  5 - When The Project Appears Impossible:
- "If an elderly and distinguished scientist says something is possible, he is almost certainly right; but if he says it is impossible, he is very probably wrong." - Arthur C. Clarke
- Just because a project appears to be impossible doesn't mean it is
- Can you adjust time, cost, performance to make it possible?
- Ways to accomplish the impossible project: 1. Change the constraints - analysis, negotiation, problem solving, requirements management 2. Get around the constraints - creativity, exploiting holes, different approaches, rethinking assumptions

Chapter 6 - Knowns & Unknowns: The Risk Factors:
- "The revolutionary idea that defines the boundary between modern times and the past is the mastery of risk: the notion that the future is more than a whim of the gods and that men and women are not passive before nature." - Peter L. Bernstein, Against the Gods: The Remarkable Story of Risk 1998
- Risk is a proposed future even that would have a significant impact on you or something you care about should it happen. Positive or negative. Above all risk is uncertain.
- Risk -> severity and likelihood
- Pure risk is all downside
- Business risk has upside and downside
- Residual risk is leftover risk after mitigation
- Secondary risk is new risk introduced as a result of solutions to the original risk
- Risk management table & responses pg 134
- Managing knowns & unknowns pg 138
- Six dimensions of project management table pg 149
- Leverage, relax, absorb = triple constraints risk responses

Chapter 7 - Project Intelligence:
- Spies pay attention to their environment
- Intelligence process - Collection, Analysis, Packaging, Dissemination

Chapter 8 - It Takes A Village To Wreck A Project:
- "Normal people believe that if it ain't broke don't fix it. Engineers believe that if it ain't broke, it doesn't have enough features yet." - Scott Adams, cartoonist, creator of Dilbert
- "Want to know if you are a leader? Look back and see if anyone is following." - Marilyn Moats Kennedy
- 4 types of managerial challenges - Martyr, Scapegoat, Hall Monitor, Peon
- 4 types of stakeholders - Positive, negative, tangential, conflicted
- 4 stages of managing stakeholders - Identify, Understand, Maximize, Manage
- There are 3 reasons to communicate: 1. You want someone to do something 2. You want someone to know something 3. You want someone to feel something or some combo of the 3
- Table page 88

Chapter 9 - Framing Change:
- I confess that in 1901 I said to my brother Orville that man would not fly for fifty years. Two years later we ourselves made flights. This demonstration of my impotence as a prophet gave me such a shock that ever since I have distrusted myself and avoided all predictions." Wilbur Wright
- Counterfactuals are examinations of what might have happened had an actual even turned out another way. A great way to analyze and cope with change

Chapter 10 - Salvaging Project Value:
- Closeout of a project is often taken for granted
- Closeout: 1. Complete 2. Turned Over 3. Closed Out 4. Value Captured

- Appendix A - Questions For The Creative Project Manager:
- Questions pg 227

Monday, October 31, 2011


Fundamentals of Project Management by James P. Lewis - One thing that I think every athlete learns at a young age is the importance of fundamentals. I have tried to take that important lesson that I learned early in my hockey career and apply it in other aspects of my life. When I found out my first consulting project would be a project management role at Nike, I went to the local library and picked up Fundamentals of Project Management.

The book is relatively short, which I actually really appreciated. Fittingly, a book on fundamentals shouldn't be extremely long and wordy. I think the book does a great job succinctly laying out an overview of the basics of project management. The book not only delved into the classic project management tools and theories but it also covered topics like team engagement, leadership, and organizational culture,

I would definitely recommend the book to anyone who wants to read a good overview of project management or to anyone who wants to learn how they can hone their skills to better deliver projects on time, within budget, and within the desired performance parameters. Below are some of the notes I took while reading this book.

Notes:

Chapter 1: An Overview of Project Management:
- PMI.org
- A project is a temporary endeavor undertaken to produce a unique product, service, or result.
- Repetitive =/ project
- Definite time, cost, scope, performance requirements
- "A problem scheduled for solution"
- Rule = people who do the work should plan it
- PM role is that of an enabler
- "Leadership is the art of getting others to want to do something that you believe should be done." - Lance Packard
- C=F(P,T,S)
- Project Life Cycle: Concept, Definition, Planning, Execution, Closeout
- Projects fail at the definition phase
- Steps in managing a project: 1. Define Problem 2. Develop Solution Options 3. Plan the Project 4. Execute the Plan 5. Monitor & Control 6. Close the Project
- 9 Knowledge Areas pg 20

Chapter 2: The Role of the Project Manager:
- The primary role of all PMs is to ensure all work is completed on time, within budget & scope, and at the correct performance levels
- Must understand mission and vision of the organization
- PM is about influencing people
- Scandinavian Airlines Story
- PM has responsibility but authority. Must use leadership and management to accomplish

Chapter 3: Planning the Project:
- Two barriers to good planning: 1. Prevailing Paradigms 2. The Nature of Human Beings
- Control is exercised by comparing  where you are to where you are supposed to be so that corrective action can be taken when there is a deviation
- No plan = no control
- To plan you must have strategy, tactics, & logistics
- Project plan is: problem statement - project mission statement - project objectives - project work requirements - exit criteria - end item specifications - WBS - schedules - required resources - control system - major contributors - risk areas
- Planning tips pg 42

Chapter 4: Developing A Mission, Vision, Goals, & Objectives for the Project:
- A problem is a gap
- Vision defines done
- Mission, vision, problem statement chart pg 47
- Mission of every PM is to satisfy the customers needs
- 1. What are we going to do? 2. For whom are we going to do it?
- Objectives: what is our desired outcome? How will we know when we achieve it?
- Risk analysis pg 53

Chapter 5: Using The Work Breakdown Structure:
- WBS developed before schedule
- Break work down to a level sufficient to achieve estimating accuracy
- Assign responsibility for each part
- You cannot give a time/cost estimate without considering who will be performing the task
- Base on historical data
- Beware of Parkinson's law and variation
- List assumptions, +- numbers, things that may skew the estimate

Chapter 6: Scheduling Project Work:
- Critical pat determines the longest series of activities that can't be done in parallel
- Unless resource allocation is handled properly schedules are next to useless
- Schedule at a level you can manage
- Diagram what is possible then deal with resource constraints

Chapter 7: Producing a Workable Schedule:
- Harder to catch up than to stay on target

Chapter 8: Project Control & Evaluation:
- Having authority is no guarantee people will do your bidding. In the end people have to do it willingly
- Give people responsibility & control over what they are supposed to accomplish
- Self control needs 1. Clear definition of goal 2. Personal plan of how to do work 3. Skills & resources 4. Feedback on progress from the work 5. Clear definition of authority to take action & deviate from the plan
- If control systems do not result in action then the system is ineffective
- The simpler the status report the better

Chapter 9: Project Control Using Earned Value Analysis:
- There are only 4 responses to deviation from the plan: 1. Cancel the project 2. Ignore the deviation 3. Take corrective action 4. Revise the plan
- One of the hardest things to do is actually measure progress
- Variance formulas pg 118

Chapter 10: Managing The Project Team:
- Project management tools are necessary but not sufficient
- If you can't manage people you can't manage a project
- Have the team participate in planning to promote teamwork
- Getting the team organized: 1. Define what must be done using WBS, problem definition, etc. 2. Determine staffing requirements 3. Recruit the team 4. Complete your project plan with participation of the team
- Rules for developing commitment pg 138

Chapter 11: How To Make Project Management Work In Your Company:
- Leadership must show interest
- Reward good project management
- Train the team
- Plan small wins for people

Chapter 12: Project Management For Everyone:
- Tools should only be used when they give you an advantage