The [Solve] Friday September 9

Trusted to Deliver

Happy Friday! We have an inspirational article for you to read this week! Tom Newman, Co-Founder of Logisolve, wrote about the Process of Failing. He does an amazing job pointing out how much we can learn from failing and use it to achieve success!

Logisolve will be at PDD 2022 this upcoming Tuesday. It is hosted by the Project Management Institute of Minnesota. We hope to see you there!

The Process of Failing

By Tom Newman, Co-Founder/Sales and Marketing


I figure I would write about something that I am really good at, Failing. To me Failing, or the process of failing, is a foundational life skill that will help you achieve success both in our professional and personal lives. There is no question I have failed a lot. For the record there is a huge difference between failing and failure. Failing is trying something that you learn doesn’t work. Failure is throwing in the towel and giving up. Failing is the foundation to any success and having your own process around failing is critical to growth both personally and professionally.

In today’s world, we all want and aspire to be successful – the awards, the undefeated season, the promotion. I find it highly unusual that we don’t openly talk about failing as often, nor do we study it, embrace it and really learn from it. It’s even hard to say out loud to others when you are failing but yet we all do it every single day. In most cases, failing is or can be viewed as a weakness but I prefer it to be a strength. After all, we gain more wisdom from failing than we do from our successes.

I have played the goaltender position since I was 7 years old and was fortunate to have played at the University of Minnesota as their hockey goalie from 1989-1993 (see pictures below). Goalie is the position where your failing is on full display. There is no way around it. Your mistakes are cheered and even welcomed. Your teammates will even look at you weird when have a really, big fail. I have failed in front of thousands of spectators and probably hundreds of thousands on TV, then only to have it written in a newspaper following day. My fails, albeit the athletic ones, were on full display.

The expectations of following a historic season (which included All American and Hobey Baker winner Robb Stauber) by going back to the National Title game was a daunting task. I was only 18 years old and needed to live up to the standards of the program, which didn’t allow for much failing, but rather continued success. As I started my first few games, success was hard to come by but there sure was a lot failing. I felt overwhelmed by the level of play, the amount of pressure and expectations to perform at an All American level which is dang near impossible at 18 years old. It really was a sink or swim moment for me. If I wanted to be a starting goalie, I had to figure it out and adapt otherwise I could be viewed as not capable and could ride the pine the rest of my career. I needed to prove to my coaches and teammates that I had the ability and skills to play at the D1 level even though the results were not there. Truth be told I also had self-doubt as well. Am I really good enough? Can I do this? Can I handle the pressure to what’s been given to me? I kept pushing and channeling a positive mindset using anything I could to build off any form of success.

That daunting experience early in my athletic career was my “aha” moment in applying failing as a learning process. Crappy goal, losing big games and anything in between all fell into this failing process. Nothing was a failure but a learning opportunity to be better. As you fail, you need to have the appropriate mindset of being positive.

In looking at Failing as a process through my experiences, some key components are:

  1. Accountability – To improve/learn, you need look at what you can do better. If it’s always something else or someone else for failing then you’re not owning your end. Control your controllables and improve. This is so critical especially when working on a team.
  2. Implementing a change – This might seem obvious but in failing there needs to be a change and you have drive to change. This should not be a rinse and repeat but rather implementing something within your control with the hopes of obtaining a better result/outcome.
  3. Result- To have something fail, an event needs to happen leading to a result. There is no “trying” to get a result. There needs to be an action from which you can get a result. “Trying” or not making a decision is a fail in itself.
  4. Detaching your identity- I believe this is a big one and really fine-tuned my thinking playing goalie. We tend align ourselves to success but not to failing. We put self worth around what we accomplish so it’s tough to allow yourself to fail. I like to think of it as a champions mindset. Your gaining experience even when your failing and it has nothing to do with your self-identity and worth. I could care less about failing. What really matters is how you respond to failing.
  5. Fail Fast- I know this is applicable in the Agile setting. If the goal is to improve, then it makes sense to move faster to get the desired result. Same rules apply in life and work.

In looking at my business career and personal life, this process of failing has been extremely instrumental in my growth and success. I have never really verbalized it but I know people see it. I realize it can even get to the point of being annoying to others around me both at work and home. It’s so engrained in my thinking that it’s hard to accept failure. After all, failure is a defined state, it’s an end. Failing is the process that is never ending which means there is always the potential of a better outcome.

How do you handle your fails?

Does your failing lead to growth in either personal and professional development?

Project Management Institute – PDD 2022

The Project Management Institute of Minnesota has a great day planned on Tuesday. They are hosting a Symposium Day and Vendor Fair! Logisolve will have a booth at the vendor fair. Stop by and say hello!

Click on the banner below for more information.

Welcome to Logisolve

Check out who is joining us in September!


Revanth V – Digital Solutions/Sr. Developer

David P – Business Transformation/Marketing

Rob E – Business Transformation/Sr. BA

Melinda H – Digital Solutions/Manual QA

Venkata D – Digital Solutions/Data Integration Developer

Joe H – Digital Solutions/Front End Developer

Josiah K – Business Transformation/Project Manager

Barry V – Business Transformation/Project Manager

Rahul G – Digital Solutions/QA

Ashley C – Sr. Art Director

Eric L – Digital Solutions/QA

Available Positions

If you have individuals in your network that may be a fit for any of the positions below, this is a great time to make a referral. Many clients are starting to head back to the office one or two days a week and are focused on local resources!

Use our referral email address:

Below are our most active Client Opportunities; contact us for more information! There are additional positions posted on our website:


Quality Assurance

Sr. QA Lead (2 positions) – highly desired Financial industry experience – must be local to MN

Sr. QA – strong SQL experience – must be local to MN

QA – API – remote

QA – financial/actuarial experience – hybrid

Project Management

Project/Program Manager – financial industry experience (prefer brokerage) – hybrid-MN


Sr BA – hybrid – St. Cloud


Sr. Java Developer (2 positions) – react, Java8, spring boot, spring – remote – must be local to MN

.NET, Ling, C#, SQL

Java Developer – Kafka, micro-services, Java 8-remote

.NET, C#, vue.JS, AWS – remote (2 positions)

.NET developer (Associate level) C#, – must be local to MN – contract to hire


EDW-ETL Administration – health catalyst experience required – remote

SQL DBA-contract to hire – hybrid – must be local to MN

Data Architect – Tableau expert – remote

Digital Analytics Manager – Data storyteller – adobe – remote

Database Developer-PL/SQ, Tableau – medical device industry experience – remote


D365 Solution Architect – Direct hire – remote

Middleware Engineer – hybrid – must be local to MN

Vendor Manager -Direct Hire – MN