Jayme Edwards https://jaymeedwards.com Software Development Coach Mon, 13 Nov 2017 23:41:35 +0000 en-US hourly 1 https://wordpress.org/?v=4.9.1 5 Signs Your Software Business Is Led By Amateurs! https://jaymeedwards.com/2017/11/09/5-signs-software-business-led-amateurs/ https://jaymeedwards.com/2017/11/09/5-signs-software-business-led-amateurs/#respond Thu, 09 Nov 2017 14:48:01 +0000 https://jaymeedwards.com/?p=5464 Get the feeling the people running your software business don't know what they're doing? 5 signs your software business is led by amateurs!

The post 5 Signs Your Software Business Is Led By Amateurs! appeared first on Jayme Edwards.


Do you ever get that sinking feeling that the people running your software business don’t really know what they’re doing? Here’s 5 signs your software business is led by amateurs!

📺 Watch on YouTube

🎧 Listen to the podcast on iTunes or Soundcloud

OR Read a summary below:

It can be practically a sport to make fun of leadership for not understanding modern software development and its implications. That’s not the purpose of this video.

If you’re working at a company where several of these signs are present, you have three options. Put up with it, try to change it for the better, or move on.

Here’s 5 signs your software business leadership needs help:

  1. Failure To Invest In Better Tools and Services
  2. Too Much Power In The Hands Of A Few Customers
  3. They Can’t Say “No” To Any Customer
  4. They Have A High Customer Acquisition Cost
  5. They Commit To Deadlines Without Understanding The True Cost

If the place you’re working at has these problems, do you have the courage to move from complaining to having some serious conversations?

Even if you consider yourself just a cog in a huge machine, you can help your leaders make better decisions that keep the company profitable!

The post 5 Signs Your Software Business Is Led By Amateurs! appeared first on Jayme Edwards.

https://jaymeedwards.com/2017/11/09/5-signs-software-business-led-amateurs/feed/ 0
How To Confront Difficult Software Developers About Their Behavior https://jaymeedwards.com/2017/11/07/how-to-confront-difficult-software-developers-about-their-behavior/ https://jaymeedwards.com/2017/11/07/how-to-confront-difficult-software-developers-about-their-behavior/#respond Tue, 07 Nov 2017 13:55:56 +0000 https://jaymeedwards.com/?p=5457 Here's some strategies to help you confront difficult software developers about their behavior so you can help them progress.

The post How To Confront Difficult Software Developers About Their Behavior appeared first on Jayme Edwards.


Have you ever been on a software project with someone who does great work but is difficult to work with? Here’s some strategies for confronting difficult software developers about their behavior.

📺 Watch on YouTube

🎧 Listen to the podcast on iTunes or Soundcloud

OR Read a summary below:

Before you even think about having this conversation, go into the converation detached from the outcome you want. If you go into it thinking “If I don’t get this person’s behavior then I’ll be upset” – the other person will pick up on it.

Here’s 6 tips for this conversation:

  1. Keep The Conversation Private
  2. Ensure They Are Well Rested
  3. Reinforce Their Value
  4. Listen For Struggles
  5. Future-Pace The Benefits
  6. Discuss Their Reservations

Don’t give the person an ultimatum! They will make the change but resent you for it!

Don’t attach rewards to the change. They will expect rewards for future good behavior!

Related Videos

Watch “My Software Development Journey

Watch “Overcoming Attachment: Discover Lean Software

Watch “How To Be A Servant Leader

Watch “How To Win Trust For Your Software Ideas

Watch “Is Wanting To Feel Important Hurting Your Software Career

Music Credits

Sonic Drifting” by Ron Gelinas

All The Beauty (original ambient version)” by Jani R

Ambient Theme No. 1” – Steven O’Brien

The post How To Confront Difficult Software Developers About Their Behavior appeared first on Jayme Edwards.

https://jaymeedwards.com/2017/11/07/how-to-confront-difficult-software-developers-about-their-behavior/feed/ 0
4 Ways Needing To Be Understood Makes Software Professionals Dislike You https://jaymeedwards.com/2017/11/02/4-ways-needing-understood-makes-software-professionals-dislike/ https://jaymeedwards.com/2017/11/02/4-ways-needing-understood-makes-software-professionals-dislike/#respond Thu, 02 Nov 2017 21:35:54 +0000 https://jaymeedwards.com/?p=5447 Today I'd like to share 4 behaviors that can stem from needing to be understood that can cause others dislike you.

The post 4 Ways Needing To Be Understood Makes Software Professionals Dislike You appeared first on Jayme Edwards.


Does it seem like others are turned off by you before you’re even able to fully explain yourself? Today I’d like to share 4 behaviors that stem out of our fear of being misunderstood. These can cause other software professionals to dislike and not want to work with you!

📺 Watch on YouTube

🎧 Listen to the podcast on iTunes or Soundcloud

OR Read a summary below:

Demanding Re-Explanation

A parent will sometimes ask a child “OK, tell me what I just said” to make sure they understand. If you do this to an adult on your project, it sends the signal that you don’t think of them as very intelligent. It also comes across as condescending.

Instead, make sure the other person understands the essence of what you’re saying. If they know enough to take action, move on.


It’s tempting when we’re insecure in some way about our skills to take apart what others say and demand it to be phrased how you would. This comes across as needy, and though you might think it demonstrates your mastery of the knowledge, it turns people off.

As with the above point, when the other person chooses to use different words than you, but they are basically saying the same thing, let it go – they get it.


In our desire to make sure we’re understood, we can sometimes verbally vomit our ideas onto a person and overwhelm them. It takes a lot of energy to have technical conversations, so plan wisely and only communicate the minimum information needed to get the other person to take the actions needed.

Abusing Apologies

In our desire to help other people feel comfortable with us, we can sometimes abuse apologies. Saying “sorry” for a mistake you made, and owing up to it, is a good idea. But if others are upset with you about something you didn’t do or had no control over it, never apologize. If you do, it sets the precedent they can use you as a punching bag.

Related Videos

Watch “How To Win Trust For Your Software Ideas


Free Ambient Loop” by Sweet Wave Audio

Sonic Drifting” by Ron Gelinas

All The Beauty (original ambient version)” by Jani R

The post 4 Ways Needing To Be Understood Makes Software Professionals Dislike You appeared first on Jayme Edwards.

https://jaymeedwards.com/2017/11/02/4-ways-needing-understood-makes-software-professionals-dislike/feed/ 0
Is Wanting To Feel Important Hurting Your Software Career? https://jaymeedwards.com/2017/10/24/feel-important-hurting-software-career/ https://jaymeedwards.com/2017/10/24/feel-important-hurting-software-career/#comments Tue, 24 Oct 2017 14:40:51 +0000 https://jaymeedwards.com/?p=5410 Once you've been in software for a bit, growing in your career isn't about you. Could wanting to feel important be holding you back?

The post Is Wanting To Feel Important Hurting Your Software Career? appeared first on Jayme Edwards.


Does it frustrate you when you see other software professionals get recognition or opportunities you want? Are you stuck in a software project situation where it feels like you’re unable to grow?

Let me share some information that will help you advance, but in a healthy way. I’ll list 4 tips at the end.

📺 Watch on YouTube

🎧 Listen to the podcast on iTunes or Soundcloud

OR Read a summary below:

Growth and Perks are Abundant Early On

When you first start working in software, you’ll have rewards that will keep you satisfied for the first 2-5 years:

  • Lots to Learn (Everything is NEW!)
  • Casual Environment
  • Good Benefits

After time spent on spent on projects that aren’t letting you grow, you may hit some barriers:

  • Continued growth may not be important to your employer
  • The path to advance may appear to be “blocked” by other ambitious professionals

The reality is that the way to grow is to contribute more. You’ll always progress faster in your software development career when you serve others with something for which you have become particularly skilled.

Why Software Professionals Struggle to Grow

You may be familiar with Tony Robbins’ 6 human needs. He breaks human behavior down into things that drive us and are necessary for our survival.

  1. Certainty
  2. Variety (or Uncertainty)
  3. Significance
  4. Love and Connection (or Team/Community belonging)
  5. Growth (Personal skills)
  6. Contribution

As software developers, we have particular dynamics to the job that cause us to get into trouble with these human needs:

Problem #1: We seek certainty, but then get bored.

Problem #2: We try to be significant (get promoted, recognized), and sacrifice connection with others.

Problem #3: We focus on growing our skills, and sacrifice contribution (helping others).

4 Tips for Healthy Software Career Growth

How can you balance these human needs better, specifically in your software career?

Tip #1: Set Deadlines for Career Changes

Don’t wait until you get frustrated. Plan for when to make career decisions if situations don’t improve.

Tip #2: Respect Resistance to Change from Others

There will be times you want to grow and others don’t. You want to get support from other people on your projects in a way that’s healthy to your relationship. Watch my video about How To Win Trust For Your Software Ideas for some tips.

Tip #3: Contribute to Other People’s Career Growth

When you help others get recognized, they will return the favor. You also get an opportunity to learn from others when you let them lead you in doing new work when you want to grow.

Tip #4: Allow Others to Be “The Expert”

When you let others teach you, instead of just learning from the internet, you strengthen your relationship. This is because people appreciate when you show that you value their opinion enough to defer to them for their expertise. It also helps you learn faster from their experience than scouring StackOverflow and Google. Being able to become a “newbie” again is an invaluable skill!

Related Videos

Watch my video “How To Win Trust For Your Software Development Ideas“.
Watch Tony Robbins’ TED Talk (He Discussses the 6 Human Needs).

The post Is Wanting To Feel Important Hurting Your Software Career? appeared first on Jayme Edwards.

https://jaymeedwards.com/2017/10/24/feel-important-hurting-software-career/feed/ 1
Overcome Attachment: Discover Lean Software Development https://jaymeedwards.com/2017/10/17/overcome-attachment-discover-lean-software-development/ https://jaymeedwards.com/2017/10/17/overcome-attachment-discover-lean-software-development/#comments Tue, 17 Oct 2017 18:28:08 +0000 https://jaymeedwards.com/?p=5393 Today I'd like to offer some strategies to overcome attachment so you can get others to use agile and lean software development methods.

The post Overcome Attachment: Discover Lean Software Development appeared first on Jayme Edwards.


Are you trying to get other people to use agile or lean software development methods, but they can’t seem to break out of the mindset they’re stuck in? Today I’d like to offer some strategies to overcome attachment.

📺 Watch on YouTube

🎧 Listen to the podcast on iTunes or Soundcloud

OR Read a summary below:

Building What Customers Want Takes Failure And Learning

Traditional management at many companies focus on predictability. They want to know how long things will take, and how much they will cost. Unfortunately if your software company wants to be innovative, you may already know that you can’t measure performance this way.

If you want to deliver truly disruptive and valuable ideas to your customers, you need to experiment and make small investments to see how customers receive them.

Establishing the Mindset for Failure and Learning

I talk often on my YouTube channel about how important experiments are to the success of your software company, and how you can sell and introduce the changes needed to work this way to leadership and other stakeholders.

Assume for a moment you’ve already convinced people of the benefits of lean software development methods that let your company experiment (DevOps, Continuous Delivery, Lean Startup techniques etc.).

Yes, people now understand the mechanics of these approaches. But it can be frustrating at first to help others have the courage to take risks and actually experiment.

This is because experimenting and then learning from the results, often requires failure.

The Uncertainty of Innovation Can Cause Anxiety

One of the technology capabilities I have said in other articles is crucial to a company sustainably releasing valuable software, is Continuous Delivery. This lets your team release your software to customers as frequently as multiple times per day.

If you’re going to let the customer take a larger role in deciding what’s in your product, and release it multiple times per day — you’ll have an increased set of feedback.

Also subject matter experts like Product Managers will find out their ideas aren’t as valuable as they’d hoped when trying new things.

These two changes alone introduce uncertainty that needs to be handled with care. Without addressing this, your team will start blaming each other and going back to what they’re comfortable with when their first few experiments don’t produce the results they anticipated.

Overcoming Attachment to Enable Learning

If you celebrate Christmas or your Birthday, you’ve probably experienced being attached to a gift or outcome you wanted as a child.

You and your team need to overcome these feelings of attachment at your company to use lean and agile methods for developing software. Without detaching from outcomes, people will feel threatened when things change.

We Must Be Comfortable With Uncertainty to Take Risks

The more comfortable you can be with trying things and not being able to guarantee that the outcome is something that you want, the more you can take risks. This is exactly the mindset needed to be more innovative with software development.

Get Your FREE Software Development Coaching Session

Strategies for Practicing Detachment

Since you know people need to be more comfortable with uncertainty, and they need to be less attached to outcomes — what are some strategies you can use to cope with this?

Thinking About the Possibility of Other Outcomes

Most people in corporate America don’t want to do this. Typical work structures are all about certainty and planning for outcomes we expect.

Instead, thinking about the possibility that what you’ve planned might not work out ahead of time primes you for a healthy mindset for taking risk.

When you’re working with a team to experiment, remind them at every opportunity that everyone is looking forward to seeing the data to help them steer the product in the right direction.

If the data behind a release shows that a change wasn’t positive, that is not a failure.

It must be clear that there will be no reprimanding for theories the team held about what would be valuable, as testing those theories will inherently prove when our ideas aren’t good.

This is the nature of the scientific method!

Beware of Catastrophizing


Once you begin to allow yourself to entertain the possibility of uncertain outcomes, it’s tempting to think of the worst case scenario. This is known as catastrophizing, and creates anxiety by focusing your thoughts on negative situations that haven’t even happened yet!

When I’ve caught myself catastrophizing, I often realize I’m tensing up and experiencing the same emotions as I would if the event happened — but it hasn’t.

Spending significant time thinking about the worst possible outcome will cripple your team with fear, and cause them to lose the courage needed to present their best ideas to your customers. Yes, there is a time for risk management — but innovation is not that time. 😀

Overcoming Resentment to Past Failures

If you hold on to negative feelings about what may have happened in the past, you won’t have the open mind necessary to try new things. Examples might be working with a person who made a mistake before, a business partner who didn’t hold up their end of the deal, or a software development task that was more complicated than first thought.

Resentment is another form of attachment. You should consider practicing forgiveness and using whatever healing tools work for you or your team to let go of any resentment.

These could be simple things like giving someone a personal apology if you played a part in the situation. Or something that lets you face the situation and let your feelings with it rest such as meditation.

Whatever physical, emotional, or spiritual activity you can find that works to help you or others involved emotionally detach from the experience, use it. Let the past go so your team can try new things with a clean slate!

Challenging Limiting Beliefs

If someone told you something about yourself as a child, or perhaps a co-worker made a statement about your skills — you may be walking around carrying an inaccurate picture of yourself. You should challenge thoughts held about what is really true with respect to the limitations you or your team may perceive about their capabilities.

I once worked with a Fortune 500 client who only released their product at night when no customers were using it. They were convinced it was impossible to release it during the day even though the technology needed to do so was common.

Until I challenged this belief, and did not back down until I heard a logical answer for why it couldn’t be done — no one had considered it a possibility.

Once everyone moved past this limitation in their thinking, they were easily on board and supportive of working with me to plan for the change.

Separating Our Identity From Outcomes

In most companies if someone makes a “bad” decision, they are held accountable. What this can do though is cause you to place your self-worth in your decisions and their outcomes. To have the courage to innovate, you need to separate these two.

People on your teams should strive to treat each other kindly especially at the times when they make mistakes. But when they slip up and get upset at you or someone else for a decision that they didn’t like, it’s important to not take it personally. You can’t control how the other person will react — but you can control your reaction to their being upset.

Practicing Delayed Gratification

Your company may need to build and release five small versions of an idea to your customer before you hit the ideal solution, when delivering a product in a lean fashion. Because of this, the management team may be lacking in the necessary patience at first to see things unfold with the product this way.

Delayed gratification is simply waiting longer to get something you want. This might sound like a silly thing to recommend, but you’d be surprised how many people I come across in leadership positions who are still very attached to immediacy. If you have people like this in key positions at your company, this may be the reason why you’re having a difficult time getting support for the changes you want made.

Practice this yourself, and with your team, to relax your feelings of urgency so you have the patience to try several iterations of an idea before settling.

Permitting Others to be Frustrated with Uncertainty


It’s natural that when trying something new, such as to not be as attached to outcomes, you and others will make mistakes. It’s crucial that everyone be willing to forgive each other when unpredictable negative outcomes occur. Without this safety net, there can be no loyalty, transparency, or ability to take risks. These are the attributes of relationships at your company that can make or break the long term health of the software development culture.

Related Videos

Watch my Scrum vs Kanban video.
Watch my Lean Software Development video.
Watch my A/B Software Development video.
Watch my Uncertainty of Software Development video.
Watch my Anxiety of Software Development video.

The post Overcome Attachment: Discover Lean Software Development appeared first on Jayme Edwards.

https://jaymeedwards.com/2017/10/17/overcome-attachment-discover-lean-software-development/feed/ 1
How To Build Consensus For Software Decisions https://jaymeedwards.com/2017/10/13/build-consensus-software-decisions/ https://jaymeedwards.com/2017/10/13/build-consensus-software-decisions/#comments Fri, 13 Oct 2017 14:03:32 +0000 https://jaymeedwards.com/?p=5375 Do you need to get people to agree and come to consensus so you can grow on your software project, or in your career?

The post How To Build Consensus For Software Decisions appeared first on Jayme Edwards.


Do you need to get people to agree and come to consensus so you can grow on your software project, or in your career? Today I’d like to share a few resources, and some simple concepts to consider, when influencing others to make a decision.


When I started out in my career, I was a good software developer and could write code and work with many complicated pieces of technology. But I didn’t become good at influencing people until I began consulting a decade later.

The Circles of Influence

Stephen Covey’s famous book “The 7 Habits of Highly Effective People”, introduces many powerful concepts for better work. I’d like to mention his concept of circles of influence, which is important for thinking about how to build consensus.

The first circle is the circle of control, and typically only includes yourself. If you have children, or subordinates, you may consider them within this circle. In most cases however, there is little you can actually control.

The second circle is the circle of influence, and is comprised usually of people on your software team who you already have good relationships with. These are people who will take your advice seriously, and expect you to influence them.

Get Your FREE Software Development Coaching Session

The last circle is the circle of concern, and includes people that we have no direct control over OR influence with. Influencing these people usually takes indirect influence through another person.

Who Can I Influence Already?

It makes sense, especially within the context of Stephen Covey’s book and recommendations himself, that we focus on those we can influence first. If we already have great relationships, those should be the first people we bring over to our side with a decision.

Identifying Stakeholders of Your Circle of Influence

Because it often takes getting agreement from people outside our circle of influence, we next need to identify who these people are. We can typically influence them indirectly through the relationships we already have. If not, we can look to someone else we know, that knows this person already, to open a door to a conversation.

You May Need to Influence “Up the Ladder”

Many software companies can grow into a structure with multiple levels of people. Even when using agile development methods, communication across people continues to be a challenge. In addition to building consensus across our circle of influence at our level, we may need to get agreement UP the “ladder” of people in the company so we can reach consensus.

Beware of Team Dysfunctions

While attempting to influence others, it’s common that due to past failures or trust issues, you may run into politics. The book by Patrick Lencioni, “The 5 Dysfunctions of a Team”, is a great resource to help you win back the support of difficult people and get everyone talking honestly again.

Related Resources and Videos

Watch/Listen/Read: How To Win Trust For Software Ideas
Buy 7 Habits of Highly Effective People
Buy The 5 Dysfunctions of a Team

The post How To Build Consensus For Software Decisions appeared first on Jayme Edwards.

https://jaymeedwards.com/2017/10/13/build-consensus-software-decisions/feed/ 1
How To Shut Down Your Feature Factory https://jaymeedwards.com/2017/10/06/shut-feature-factory/ https://jaymeedwards.com/2017/10/06/shut-feature-factory/#comments Fri, 06 Oct 2017 19:24:29 +0000 https://jaymeedwards.com/?p=5161 Are you developing software under pressure like a "feature factory", but there never seems to be any economic benefit to the changes?

The post How To Shut Down Your Feature Factory appeared first on Jayme Edwards.


Are you developing software under pressure like a “feature factory”, but there never seems to be any economic benefit to the changes? Today I’d like to share some strategies to begin shutting this unhealthy work approach down.


The term “feature factory” was coined by John Cutler, a Senior Product Manager currently at ZenDesk. He wrote an article in the Hackernoon publication on Medium here that introduced the concept to the masses.

When you read his article, you may, like me, find yourself nodding your head “YES!” to all of it. Anyone who has worked to produce software on a team that is a feature factory will immediately recognize many of the symptoms.

What is a Feature Factory?

I’d encourage you to read all of John’s articles for more details, but when you really boil it down a feature factory is a team or company that doesn’t know how to measure the business impact of their changes.

Set a Measurable Business Impact Goal for EVERY Change

When we’re in school many of us learn the scientific method. At a high level – you have a theory, you decide how to measure it, you design an experiment, and you record the results. Often our theories are proven wrong.

Unfortunately, when it comes to developing software many of us assume we can’t be wrong and do very little to handle that very real possibility. One of the first things that is necessary to shut down a feature factory, is to only make changes that can be measured as being successful or not in reaching an outcome.

Move Further Towards Cross-Functional Teamwork

When the people who work together to produce software are in separate departments, it often leads to people deferring design decisions to a UX, Product Management, or other design person. A cross-functional team actually strengthens the ability to deliver “the right thing” and NOT be a feature factory, because everyone can contribute to design ideas because they are dedicated to the success of ONE product.

Celebrate Outcomes Instead of Releases

When we start releasing software several times a day using things like DevOps and Continuous Delivery, we often will not hit a positive business outcome with each release. Because of the chance of failure, we should celebrate as a team when we reach a business outcome – not every time we release. John calls this “success theatre”.

Cultivate a Culture Safe for Failure and Learning

When we plan a project that takes a long time to deliver, during that period there are assumptions about the value of what’s being built. There are no ramifications or learning until the end, and on some teams if the product doesn’t deliver on it’s expectations people are FIRED!

Get Your FREE Software Development Coaching Session

To allow teams to be innovative and discover what they truly want, you must release small changes with the expectation that these may be “wrong”. This requires making it safe for Product Managers and others to take risks so they can learn.

Focus on Value NOT Efficiency / Utilization

This one is pretty self explanatory. If a team is constantly pushed to be as efficient as possible, they won’t have the relaxed and creative mindset necessary to make changes that contradict our initial assumptions!

Release Smaller Changes, More Often

To enable failures (learning) to have a smaller impact and cause less waste when it comes to budgeting – designing changes (experiments) that can run as FAST as possible and give us feedback EARLY is crucial.

Additional Links and Related Videos:

Watch my video on Lean Software Development here.

Watch my video on Cross-Functional Teams here.

Watch my video on Continuous Delivery here.

John Cutler’s articles on Medium: https://hackernoon.com/@johnpcutler

Learn more about Psychological Safety by following Ashley Johnson and Tim Ottinger

The post How To Shut Down Your Feature Factory appeared first on Jayme Edwards.

https://jaymeedwards.com/2017/10/06/shut-feature-factory/feed/ 1
5 Ways Dishonesty HURTS Your Software Development Career! https://jaymeedwards.com/2017/09/11/5-ways-dishonesty-hurts-your-software-development-career/ https://jaymeedwards.com/2017/09/11/5-ways-dishonesty-hurts-your-software-development-career/#comments Mon, 11 Sep 2017 18:33:11 +0000 https://jaymeedwards.com/?p=4376 Today I'd like to share some ways dishonesty hurts your software development career, including past ways I have been dishonest that I now see are common.

The post 5 Ways Dishonesty HURTS Your Software Development Career! appeared first on Jayme Edwards.


Do you find it hard to be honest with others about some aspect of developing software? Or maybe you find others are withholding truths, and you wonder why? Today I’d like to share some ways I have been dishonest earlier in my career, and I now see are common in our industry.


Not Admitting Being Unfamiliar With Something

In short time, we can gain a lot of knowledge about technology and software development processes. If we’re not careful, this leads to a “big head” or inflated ego, and we can feel embarrassed if we haven’t heard about “the new hotness”. If we’re honest with others when we don’t know something, they trust us more to be transparent, and they know they can share things they are excited about without us shutting them down in an attempt to be seen as the expert.

Saying “Yes” To Work You Don’t Understand

It is often that on software projects we are asked to estimate work based on the information another has captured for us. If we don’t fully take the time to understand it, or have a self-inflated sense of our level of skill, it doesn’t take much to agree to work when we shouldn’t. I learned to say “No” more strongly and honestly about 5 years ago, and it has helped me on numerous occasions. When I didn’t do this, I would often put myself under extra pressure, and have to reset expectations with the other party who is now upset that I can’t deliver what they expected.

Not Admitting We’ve Overlooked A Process Step

Software development is inherently complex and often requires many moving parts to be changed in a very specific sequence to accomplish work. As humans, we will inevitably make mistakes. Under pressure, I have failed to be honest with others that I simply forgot a step in my desire to be seen as the expert.

Get Your FREE Software Development Coaching Session

I have become MUCH better about being honest about this now, but it is very common in more junior technologists. When we take responsibility for forgetting something, we build trust with others who know we will hold ourselves accountable for our actions.

Making Generalizations About Others

In our desire to be seen as the expert, we can sometimes have just a few interactions with another person and then paint them as incompetent or lacking in skill to others. This thinly-veiled attempt to make ourselves appear smarter than we are casts doubt in all but the most unsophisticated of people. If the person you made a generalization about meets the person you said this to, they will find out that you are quick to judge and make inaccurate statements on a whim. Just don’t do this!

Not Being Honest About Your Level Of Contribution

We work hard to produce quality deliverables and value for our team and customers on software projects. And few things feel better than a customer or someone else at the company saying “great job”! But I have not always been as forthcoming about the work others did to support me in successes, and since getting better at this my ability to motivate others and build trust has gone up tremendously. When you check yourself when receiving a complement and remember to include others who were part of the success, you build a positive emotional connection between you and them, and deepen the trust and loyalty necessary to keep a strong team together.

#softwaredevelopment #softwareengineer #softwareengineering #softwaredeveloper #softwarearchitect #softwarearchitecture #agile #lean #scrum #kanban #productmanager #productmanagement #digitalproduct #digitalproducts #career #culture #softskills

The post 5 Ways Dishonesty HURTS Your Software Development Career! appeared first on Jayme Edwards.

https://jaymeedwards.com/2017/09/11/5-ways-dishonesty-hurts-your-software-development-career/feed/ 1
My Software Development Journey (Part 3) https://jaymeedwards.com/2017/09/11/my-software-development-journey-part-3/ https://jaymeedwards.com/2017/09/11/my-software-development-journey-part-3/#comments Mon, 11 Sep 2017 18:25:35 +0000 https://jaymeedwards.com/?p=4372 Would you like to know more about who I am and how I became passionate about lean methods? Let me share part 3 of my software development journey with you.

The post My Software Development Journey (Part 3) appeared first on Jayme Edwards.


Would you like to know a little more about who I am, and how my successes and setbacks shaped me into someone who is so passionate about doing less at one time, and embracing uncertainty as part of a lean software development mindset? Today I’d like to share part 3 of my software development journey with you.


Agile Theater: Alive And Well

What my consulting experience had shown me so far, was that many companies still struggle to do agile development. They use some of the technologies and processes, but they have a difficult time transforming the minds of leadership and key players to support true agility.

First Startup: Social Network / Time Tracking For Home Schoolers

I got the idea for and began building a social network for home schoolers about 6 years ago. The product was built in ruby on rails for speed to market, and being a Father of 3 home schooled children myself, my wife and I knew some of what we thought others would want. Unfortunately, I fell into the classic “Subject Matter Expert” trap! I had a “knowing / doing gap” where I could help OTHERS do lean software development, but when it came to MY ideas, I was just as stubborn! In the end I stopped working on the product as I had built too many things that were not useful to my customer, and market analysis had me wanting to pursue a different market.

Becoming (Unwillingly) A Firefighter

Around this time my day job in consulting began sending me in to help fix issues at projects with our clients that were in trouble. I got good at this, but it began to burn me out as I started seeing the same quality issues from both our consultancy and the client. The root problem was that the way we engaged with our clients did not embrace agility, and so when things changed or we learned we’d failed in some way, it was costly and slow to adapt.

Resistance To The Shift Towards Lean

I began to put together a set of content and team that would have the skills at my consultancy to start delivering in a more lean fashion, but the leadership did not yet have the courage to support me even after numerous presentations, discussions, and wins. By the time they began to invest, it was too late – our competition had a several year lead on us.

Second Startup: Public Health Data Analysis

A friend of mine whom I’d worked with for many years brought an idea to me for a product and was gracious enough to ask me to be involved. There were a number of problems as we began building the company though. First, we both had day jobs and children, and the personal investment was too high to be sustainable for our initial offering. Second, we weren’t clear on our lines of responsibility and so our relationship was taxed.

Get Your FREE Software Development Coaching Session

Third, the technology landscape around the “big data” tools we were using were too immature, and there was too much rework we needed to do to deliver the minimum viable product (MVP). Lastly, we failed to deliver small enough ideas before getting feedback, and fell again into the “Subject Matter Expert” trap by overbuilding.

A Burning Desire To Be Lean

I finally read “The Lean Startup” by Eric Ries and it opened my eyes to some of the things I had been doing wrong. As I began trying to apply these techniques with clients, I came up against confusion created by vendors in the industry who focus on technology that is “lean” or “agile” but don’t help companies truly adopt the lean mindset. Battling this became the current focus of my career.

Using Small Batches To Improve Product Management

I wanted to help the people driving the direction of the product to learn whether they failed or not with less investment, and faster, so they wouldn’t make the same mistakes I did. To do this however requires creating the psychological safety necessary for failure and learning. And to get support for transforming the culture to support this safety, consulting skills are necessary.

Supporting Your Lean Transformation

Eventually, I started a membership program to help mentor software professionals to get the support for consulting and lean skills necessary to help them transform their company’s culture, or use lean techniques for their own startup ideas. I am focused on helping people use the scientific method, as described in the Lean startup; relationship skills and personal development to become a better communicator and persuader; and Continuous Delivery technologies such as the cloud and automation technologies – all in an effort to be more successful.

Referenced Videos

Watch Part 1 here, and Part 2 here.

Watch How To Win Trust here.

Watch How To Fail Faster here.

Watch About Minimum Viable Products here.

Watch How To A/B Software Development here.

#softwaredevelopment #softwareengineer #softwareengineering #softwaredeveloper #softwarearchitect #softwarearchitecture #agile #lean #scrum #kanban #productmanager #productmanagement #digitalproduct #digitalproducts #career #continousdelivery #devops #leanstartup

The post My Software Development Journey (Part 3) appeared first on Jayme Edwards.

https://jaymeedwards.com/2017/09/11/my-software-development-journey-part-3/feed/ 1
My Software Development Journey! (Part 2) https://jaymeedwards.com/2017/09/11/my-software-development-journey-part-2/ https://jaymeedwards.com/2017/09/11/my-software-development-journey-part-2/#comments Mon, 11 Sep 2017 18:15:48 +0000 https://jaymeedwards.com/?p=4368 Would you like to know more about who I am and how I became passionate about lean methods? Let me share part 2 of my software development journey with you.

The post My Software Development Journey! (Part 2) appeared first on Jayme Edwards.


Would you like to know a little more about who I am, and how my successes and setbacks shaped me into someone who is so passionate about doing less at one time, and embracing uncertainty as part of a lean software development mindset? Today I’d like to share part 2 of my software development journey with you.


Letting Go Of “My Baby”

After my first project that was both a product I designed and an opportunity to lead, I was given the opportunity to start a new one. It was difficult to let go of the success I’d had, and hard work I’d done, of this first project so early in my career.

Release Deadline Sabotage!

Soon the head of the company mandated that all products across the company release on the same day every 6 months. He had no idea what this took, but at the end of the day my team’s project was the only one ready. For political reasons, it was sabotaged by changing the name the last week of the deadline!

Following The Leader To New Opportunities

After our project was sabotaged, my boss was unfortunately fired and took the fall, and he moved on to a new company where I followed shortly thereafter. This new company was in the pharmaceutical space and needed the kind of help my old team at the prior company could provide, so many of us switched over.

Pioneering Agile

We built a simple web portal that let us track our sprints and other artifacts related to agile. This was before tools like Jira, Pivotal Tracker, or Team Foundation Server were available. It was crude, but we learned a lot and through our mistakes and successes became very early proponents of Scrum.

Family Conflicts Of Interest

Unfortunately there was a miscommunication between my boss and his, and my boss took the fall AGAIN due to company politics wrapped up in family ownership.

Get Your FREE Software Development Coaching Session

I was extremely frustrated at this point after seeing my boss, who I considered one of the best leaders I’d worked with, continuing to be sideswiped by politics.

My First Architecture Consulting Experience

I followed my boss again to his next company, and got a chance to provide architecture consulting services. We helped them ship a late product, and created a prototype of a new one in ruby on rails over that year.

Moving To Austin, Texas

Eventually my Wife and I wanted a change, so we moved to Austin, Texas. The lifestyle and career options were more in line with what we wanted at the time, and we’re still here today as of 2017.

Moving Into Consulting

Shortly after arriving in Austin I was contacted about a consulting opportunity. Though it was a little less than I wanted compensation wise, I was excited about the chance to learn a different way of providing IT services and took the offer.

Getting An Ego Check-Up

I frustrated several clients in the first 2 years I was a consultant, and had a reality check. During my performance review I was criticized (rightfully so) for my inability to talk and relate well with clients.

Setting The Intention To Improve My Soft Skills

After the deflating performance review, I emboldened myself to learn what I needed to “get” this consulting thing. I came across the book “Flawless Consulting” by Peter Block after my wife purchased it to help her with Nutritional Health Coaching.

Learning To Be A Trusted Advisor

The first time I applied the info in Flawless Consulting was a game changer. I could win the trust and advisor status with a client almost immediately through these strategies!

Discovering Continuous Delivery

While working for a large international grocer based in Austin, I read the book on Continuous Delivery by Jez Humble. This had a huge impact on me and caused me to focus my career almost solely on mastering it.

Teaching Clients About Continuous Delivery

After creating a framework in Windows PowerShell that helped me implement Continuous Delivery at clients, I began to be frustrated that though we helped them release multiple times per day, their planning and budgeting process still didn’t allow them to BENEFIT from this new capability.

Discovering Lean Startup Product Management

This led me to learn more about Eric Ries, and eventually read his famous book “The Lean Startup“. I’ll talk in Part 3 about how I discovered how important this information was through 2 startups I failed to find market fit for.

#softwaredevelopment #softwareengineer #softwareengineering #softwaredeveloper #softwarearchitect #softwarearchitecture #agile #ux #productmanager #productmanagement #digitalproduct #digitalproducts #career #leader #leaders #leadership #relationship #relationships

The post My Software Development Journey! (Part 2) appeared first on Jayme Edwards.

https://jaymeedwards.com/2017/09/11/my-software-development-journey-part-2/feed/ 2