A "People First" Blog.

Saturday, July 25, 2015

There Are No Problems, Only Wants

I got to talk today on one of my coaching calls about problems and wants. Let's call him John and call her Sally. First there are no problems, only wants. The real question is, "Why do I want what I have chosen?" In this we can choose again. As long as it is perceived as a problem we are insisting it remain a problem.

As John and I ended this conversation we explored the deflection and projection of our vocabulary when coping with the things we most identify with in others. We reflected back on why we want the things we choose to see in others. This clarity will always lead us to trust and power.

As we established some agreements one stuck out in my own life: We will allow the perception to serve as a self indicator of something we want to change in ourselves, We Began.

"By agreement we allow our perceptions to serve as an indicator of what we most want to change in ourselves."

The deep dive we took was on the idea that problems are ego based and only part of perception. With a fundamental understanding of the cycles that result in our perception of problem, we chose to take a deeper approach. If there is a problem, then we intend for it to recur. This is to say that we want everything that is true in our lives and that problems become the justification for continuing unhealthy behavior that on some level, we want it.

From this approach we can look at the reasons we "want" to feel this, see this, continue to go through, and O-M-G, do it again next time.

Here was today's "problem" - She always does these things and it causes me to act just like her.
While I'm removing the names and the context, I could immediately see a few things and John seemed to be unaware. First thought, do you love her?

My second thought response as an advisor was to point this out. My response as a coach was to let it sit on the table without response. Together we began to look at it and I let some time pass to see if he would hear what was just said. Eventually I asked, does Sally really "always" do this? And the answer was no. Does Sally "cause" you to do things? Again, the answer was no, not really. I thought not really an interesting point to note in my observations.

If you've found yourself saying something along these lines or thinking this, please read on. We are talking about a victim mindset here for a later post. For now, we look at how we enter these spaces of thinking, and I want to understand what we get out of it.

Since she doesn't always do this, and she can't cause anything for us, then let's talk about why we want this for us. The answer bear in mind is simple, we get something out of it. I wanted to get John to this realization in his own journey. Our conversation turned to a few points we've agreed to explore further as we work together:

"We are always at choice and
we choose because we get something out of it."

As we discussed the past I noticed allowed behaviors that seen over and over can became an expectation for John. I wanted to know if he would see it too. We discussed how this was his personal contribution to the continued cycle. The experience of the past being allowed to play out unaddressed for so long, it had become a trigger and as a result, a certainty in their communication.

When we allow things to happen for a long time and begin to expect things there are consequences. We prevent others from changing in our eyes and erode the trust that keeps the relationship sacred. By expecting certain behaviors, John was actually taking part in creating them. At the very least he wasn't allowing Sally any opportunity to behave any different. *ding* there it was for him as he said it himself. "I stand in her way of giving me what I want and she's continues to stay with me."

I asked John if he tested the relationship or jus Sally.  After a long pause and a perplexed look, I went on to explain. In these times we operate from fear, I often find another cycle that stems from no trust. Something I call "The Tests".  In these tests, we are not communicating. More likely we are looking for confirmation bias in our fear of a response to be right that we will always find it, blame, and further erode the trust. This isn't productive for what we really want out of the relationships with the people we interact.

John and I acknowledged one another and chose to create a list of the things we want to work on. Here are our next steps and metaphors to continue understanding how our behaviors reinforce what we truly want so that we may change habits:

1. Fear and Expected Response - Catch and Release

2. Allowance of our own behavior and others' behavior contributes to our perception - Maximizing Healthy Allowance

3. Trust is at the root of all behaviors observed - Are we there yet?

4. We always get what we want. The question is "Why do we want THIS again?"


In reading, do you find yourself with these thoughts? Are you aware of your contributions to the behaviors you observe in your relationships?
First, be grateful you have the opportunity and awareness to face it.
Second, own it.
In the end, let us agree the people are not a problem. #peoplefirst



Scotty Bevill
CSM, CSP, CELC, CPC, PMI-ACP, PMP, LGAC


Scotty is a CSM, CSP, PMI-ACP, PMP, CELC, LGAC, and accredited Leadership Gift Coach, and active public speaker. After spending more than 14 years with the military and 9 years working with team structures, he focuses his time on improving organizations and mentoring individuals in scrum, agile, and leadership coaching around continuous improvement and product delivery.

Thursday, July 23, 2015

Everyone Has a Story

"Everyone you meet knows at least one thing you do not."

I started a journey with this premise and remind myself this most when I think about my day starting. Each morning I look out a hotel window or balcony focused on the air. The smell, the density, the clarity. Every city has its own air just as every person as their own story. 

There are so many perspectives on experiences and we all go through. The day starts and I walk down a hallway hearing the children of parents hurrying to prepare for their vacation day and mentally I visit what it may be like in their shoes and the flow of their morning. Turning the corner and, "Excuse me." as I bumped into a cart belonging to someone cleaning a room. A local most likely working the hotel, starting their morning through the back door and then bringing the linens to all of us to start our day.

As the elevator opens and the sounds of plates and silverware clinking I think about the hours that have passed for the people preparing this buffet from cutting fruit to filling coffee and there they are...the people like me that are discussing strategy, sales, and planning for the clients or co-workers they will meet soon. 

As I drink my coffee and juice I scan the room each person talking about their ideas about circumstances and how it relates to their own experiences. To visit everyone isn't a possibility, but to realize that every one answer and every idea is a right one. I feel part of cycle that is larger than my own plans for the morning. I am glad to be here. 

I've heard it called "People Watching" and it reminds me how silent I've been all morning. As I think about how aware of my surroundings I am I realize how many times I was caught up in a conversation in this same situation unaware of all that buzzed around me. Taking time to think about my coaching and my interactions with the world is a moment I intend more and more often. 

As a coach, the more I learn the less I have to say. I realize most answers come right from the source if the story is spoken long enough. In my coaching calls this listening becomes comfort zone and an opportunity to be as present as possible without seeing "where this is going" or "knowing where it has been." The message I wanted to send today was one of story. My story, your story, and their story. Listen. Many of the stories around us just pass by on a city street or a busy hotel lobby and if you're willing to listen, you may be surprised what you learn about yourself. 



Scotty Bevill
CSM, CSP, CELC, CPC, PMI-ACP, PMP


Scotty is a CSM, CSP, PMI-ACP, PMP, CELC, and accredited Leadership Gift Coach, and active public speaker. After spending more than 14 years with the military and 9 years working with team structures, he focuses his time on improving organizations and mentoring individuals in scrum, agile, and leadership coaching around continuous improvement and product delivery.

Wednesday, July 15, 2015

Distinctions: Qualified and Capable



I had the pleasure of discussing the importance of distinctions in business and working environments. Lately I found on the web more and more discussions about coaches and consultants discussing distinctions with their clients successfully navigating things like: market confusion, vocabulary, philosophy, and approach. I want to say, I couldn't agree more. I too have now put some focus on making distinctions for the sake of sharing reality and truly communicating with one another in our context.

I know that last sentence sounds familiar to many of you, but what exactly does it say?
(that's another post -> here)

One distinction that came up recently for us in our coaching circle was that of being qualified or capable. In fact they are different things.

Here were our agreements:

- Qualified is meeting the pre-requisites for the environment, the job, the culture, and the intentions of the hiring authority.

- Capable is the ability to perform the requirements of the work necessary to reach a relative degree of satisfaction. "Good Enough Business" we called it jokingly.

Qualified discusses certifications, degrees, accreditations, and other "third party validations." In my years as a professional I see things like "Bachelor's Degree" as a minimum requirement only to see the person hired not satisfying this constraint. As of late we see more and more the companies are listing some credentials as a "plus" or "preferred". Being of an agile mind and spending my life mentoring tomorrow's leaders, I concur with this trend of making the exception in the face of demonstration. As leaders our qualifications also include integrity, responsibility, personal accountability, and ethics.

Capability is more difficult in hiring decisions and comes back to experience, representation, and demonstration. It is here we find enough empirical evidence and results focused questions. It may start in the initial interview and follow on to our references or examples of deliverables in past work.

Let's take this example: One can't be the President of the United States unless h/she is at least 35 years of age and born in the United States. While a 28 yr. old may be capable of being a great president, he/she is simply not qualified for the position.

Note: The slippery slope for all of us is temptation. It may be here that representation becomes the consideration as résumés are produced for the sake of being recognized above the other candidates. While the best of intentions are at play, the integrity and trust become the most important guide posts. Advice: Stay the course here, you are perfect exactly as you are.

The last topic that came up was one that we seem to find ourselves faced with at every juncture. Risk. The risk of hiring the right person that may not be qualified over the false comfort we may find in simply following the letter of the  job description.

It seems even in the most open of spaces, there are still considerations of risk and mitigation for the safety of the company, its officer, its employees, and its customers. The question for the company is how much risk can we assume to get the right person in the right job without limiting our own ability to succeed.

The answer is consistently: People First. Give 'em the chance to surprise you and they usually will.


Scotty Bevill
CSM, CSP, CELC, CPC, PMI-ACP, PMP, LGAC



Scotty is a CSM, CSP, PMI-ACP, PMP, CELC, and accredited Leadership Gift Coach, and active public speaker. After spending more than 14 years with the military and 9 years working with private team structures, he focuses his time on improving organizations and mentoring individuals in scrum, agile, and leadership coaching around continuous improvement and product delivery.

"Seize the day; pay it forward and backward."

Monday, May 11, 2015

7 Hidden Impediments of Great People

7 Hidden Impediments of Great Minds

We all have them and when we are working toward achievement, they can be a source of great willingness and capability. As you may have guessed here; in a collaborative environment, these may erode our very efforts if we aren’t aware and clear when they’re present.

  1. Objective vs. Subjective Chosen Reality
    1. Subjective reality is a choice to evaluate the entire world around us                                             Allows for comparison and averts the value discussion
Bigger, Faster, More, Less, Better, Worse
    1. The Case of the Mondays
                                              i.     Monday is only an idea, albeit an idea we agree to share.
1.     Even the Gregorian calendar must be updated to maintain its relevance every year. As a society we are conditioned by this to think about time as a fixed linear method in which “life goes on”. In fact, it is merely a perspective (lens) we agree to perceive a cycle life through. (Note: we also tend to agree that it is “a cycle of life”). We call this a cognitive dissonance and it is hidden in our everyday language and thought patterns.
2.     So why are Monday’s bad?
a.     This is a choice. We plan our projects and our work around a 5-day workweek, then we may spend Friday not working as diligently and we planned. As a result, Monday is overwhelmed with everyone coming back to work or extra things to get done and become very busy days.
3.     Another perspective: Imagine for a moment you are on a delivery team that deploys product every Tuesday. How would your days be affected by the co-workers that leave early on Friday, take Monday off, and the people that did come in are all having a ‘bad’ Monday?

    1. In an objective reality, things are more importantly true or false, not right and wrong. In our day we have approx. 70,000 thoughts and work with hundreds if not thousands of creative minds all around us. Accepting things as not a problem, but only a problem we perceive is the beginning of an objective perspective about any situation.
  1. Expectations
    1. How many times are “setting expectations?”
    2. How well do you respond when someone sets expectations on you? As leadership thinkers we have an alternative response. Acceptance. Do you want others to accept when you fail and allow you to grow as a result of that failure? Of course you do, me too.
    3. Michael J. Fox said – “My happiness grows in direct proportion to my acceptance, and in inverse proportion to my expectations.”
    4. When teams make agreements and practice integrity (doing what you say), then acceptance of failure is our contribution to this culture or ecosystem. Can you accept that things will go wrong? Can you respond differently to the world around you without abandoning responsibility through blame and obligation? Of course we can!
  2. Competition and Leadership ARE mutually exclusive
    1. Competition as a mind-set not a behavior is the impediment
    2. Perceiving that someone must lose for us to win may sound like a harsh way of putting it. I might offer that’s because it is how the thought works
    3. Whether a company, a project, or a co-worker; competition is not what we want. It may appear that way to us when trying to get a client, or pay raise, or a job promotion, but great leaders are looking for cooperation.
    4. When cooperation (leadership behavior) is observed the natural response in observers is to ‘covet’ or want more of what we see. This response creates and abundance in circumstance and the Law of Attraction does the rest. Eventually there is more work going on that any one of us can handle and the objective truth sets in. There is more than enough for everyone to have what he or she wants and want what he or she has. Are you willing to help anyone be successful for the sake of everyone being successful? This will get returned to you.
    5. When competition is perceived, our quality goes down, the customer/boss/observer will see the tension and resistance. This creates a scarcity event and then you are right, there is now only one opportunity and if you don’t get it someone else will.
    6. When it comes to all things, if you think it, you’re right so why not think win!? This is to say if I see there is only one opportunity, others will see that I see it and there will only be this one opportunity. But if I can look upon it without memory and see it for the first time everytime, we can get it done together!
  3. Context
    1. Context is everything!  We’ve all heard this one before, but does it mean we must share context in all that we do? Of course not. We are valued for our specialization and skills.
    2. Consider the expertise we value in an implementation coordinator and the quality that this role provides to the organization based on the expertise. Losing this passion would remove the capability we have at implementation. In our newly collaborative methodologies, this individual is now in the divergent (planning and visioning) phases of our products. We may hear things like, “that won’t work” or “here is why we shouldn’t”
    3. In a context sharing agreement, I would ask “Just for now” can we share context so that we may leverage your expertise in the output of this phase of the process. This creates a quality event that builds the team and allows for a shared reality while still acknowledging the value of the expertise.
  4. Advocacy (and Inquiry)
    1. How sure are you that you “know” something?
    2. Observation of a situation begins with questions. Asking these questions aloud gives the other team members the opportunity to dispel any unseen or unconscious assumptions you made have made.
    3. Listen for phrases like, “All I know is…”  or “Here is what I know” are signs that inference has occurred. This is not to say what is about to be declared is inaccurate. It IS is a voice inside your head that asks, Are you sure you actually KNOW this?
  5. Worry
    1. Safety First Culture
    2. When we perceive things have gone wrong, we’ve been taught to revert to past “safe” behaviors. These are not necessarily the behaviors that work, but behaviors we have associated “acceptable outcomes” with.
    3. CYA responses erode trust, abandon ownership
  6. Status Quo Value Thinking
    1. “That’s the way we’ve always done it here” is not a value statement.
    2. Team Member evaluations based on metrics that are no longer of business value become only valuable to the evaluator.

Tuesday, April 21, 2015

Agile Teams: Facilitating Issues and Change

It's April 2015 and we move back into our team focus of strategy and empowerment. In today's post, let's discuss grooming a backlog with facilitation.



In our personal coaching we've discussed some of the mindsets we (product owners, scrum masters, team members, and leaders) want to sustain for approaching any problem. By using facilitation we empower the room to subtract the impediments that traditional meetings can suffer from. Invalidation, context (shared reality), and bias are of the most common we see in our work.

Let's take a scenario for context.
We are in the middle of a sprint, the team is working on an existing prioritized and healthy sprint backlog. The product owner leaves a meeting with new ideas about product direction and impacts to the release plan. We know the next step is to prevent the impact to the team and let them work. We also know that the information coming to us is VALID. So what do we do?  Facilitate it!

Years ago I created a game called, "Get it out of your head." Working with Luke Hohmann to integrate Innovation Games® into all of our practices, I knew we wanted to over come the issues associated with invalidation/validation. (At the time of course, I only understood this to be an impediment that different personality types weren't participating in our project storming sessions). So what happens next is the strategy that has served us well every time.

1. Get a clear wall and write down everything that is an issue.

  • Stickies on a wall!
  • This is a place to see cause and effect, process problem perceptions, and get the ideas out of the product owner's head so that we can get present. Some call this sharing of reality..."context". This give us a place to put all of the ideas we have in one place so that we may process them and keep moving. It is near impossible to focus on one topic while trying to remember everything else there is to discuss.
  • In more mature environments, these issues, risks, and new stories, may have an epic (theme) or bucket to reside in for discussion before the product owner comes down to discuss them at all. This I've found tends to emerge rather become the first place we start (VersionOne does this very well)
2. Affinity Group (Shape)
  • This give us a chance minimize the number of considerations into coherent groups that are relate or dependent so we are talking about whole features and not just issues. You may be thinking this has a by product later when these become stories for the team to ingest into the workflow. And you would be correct, great catch.
  • With the ideas in groups, they become "chunks" and are easier to see visibly and reduces the stress associated with so much work or impact.
3. Prioritize Quickly 
  • The product owner probably has a pretty good idea of what's most impactful from their perspective already so this should all go very quickly between even just the two of you. 
  • By this point, there should be enough information to see how these become stories for the backlog, the situation is diffused, and the team remained in their zone doing that they do best.
In this process of Get It Out of Your Head, Affinity Grouping, and Prioritizing, we have taken divergent information and removed the emotions associated with change from the workflow. The product owner has a sense of validation in what they brought, value was created, and the team will be able to respond when a time is more appropriate to consume the information. 

When the team is ready to discuss this new information there will be new details that emerge from their input and the final stories, acceptance, and consumption (release information) can be determined as single cohesive team including the PO. 

It is important that we focus on the mechanism of acknowledgement and claiming the wins. This behavior becomes repeatable as the team matures and eventually will be anticipated behavior. How have your teams overcome this interruption as an opportunity to build the team? 


Scotty Bevill
CSM, CSP, CELC, CPC, PMI-ACP, PMP, LGAC



Scotty is a CSM, CSP, PMI-ACP, PMP, CELC, and accredited Leadership Gift Coach, and active public speaker. After spending more than 14 years with the military and 9 years working with team structures, he focuses his time on improving organizations and mentoring individuals in scrum, agile, and leadership coaching around continuous improvement and product delivery.

"Seize the day; pay it forward and backward."