About Tyner Blain


Information about Scott Sehlhorst in the About the Author page. Scott’s profile on LinkedIn.

You should read Tyner Blain because…

There’s room for improvement in software development.


Great software requires great business decisions.

  • We have to know which problems to solve, and which problems to ignore. At the core, this is business. Business drives investment in software creation.


Great software is a pleasure to use.

  • Does your job energize you or drain you? At the start of the day, are you excited to get to your desk and tackle the latest challenge? Or are you just marking off days on the calendar hoping that your position isn’t eliminated or outsourced? If you’ve got the right job, you know it in the mornings. Software is the same way. Does a user look forward to running our software, or is it a neccessary evil of getting the job done? This is art.

sehlhorst at top of spire

Creating great software is the pinnacle of achievement.

  • There’s an elegance in technical achievement. Solving hard problems is its own reward for many people. Efficient and maintainable, high quality code, can be breathtaking (to some!). There’s a science to writing software. And arguably, good implementation design is its own artform. Execution is another area where there is huge room for improvement. Gurus, companies and entire industries have cropped up to help us be better at creating software.

What is software product success?

  1. Defining the products that are destined for success.
  2. Executing successfully to create those products.
  3. Working with “everybody else” to make sure our products come to life.

Most software isn’t great. Some people argue that its just plain lousy. There are a lot of reasons, but the thing that most teams fail to do is correctly identify what the software should do. And when teams make bad decisions about what should be done, it doesn’t matter how well they execute. We write a lot about how to define the right software. We look at frameworks for describing software and methods for defining it. And we talk about how to work with the “everybody not on the team” to make sure that we get the opportunity to build our software.

Our goal is to create a community of people who agree about the importance of making the right decisions about what to build. Without the knowledge and skills needed to create software, all of the theory in the world about what software to build is worthless. We want to make sure that everyone who understands how to define great software also knows how to build it. And even with the proverbial better mousetrap, there are real-world concerns about how to drive the right investment decisions.

But why should I read Tyner Blain?

  • Because you want to learn more about those other areas of software development.
  • Because you want your company to dominate its market niche.
  • Because you want to refine your expertise with new ideas.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.