We take a break from our interviews and a wealth of recommendations to review how to apply these.  There is a technical fit and organizational fit for solutions of all types.  It is critical that you know how these may fit your specific situation.

Technical Fit

The idea of technical fit is possibly the easiest to see from the outside.  There are specific requisites in the solution that must match the problem definition.  For example, a development shop that uses C# for its code will not benefit from a Java code generator.  There may be some helpful output.  However, it will not fit the development standards.  Thus, there is little difference in a process or other non-technical solutions.  You may see constraints related to resources, budget, speed, maintainability, or other areas.

Those include solutions for business growth.  In a simple example, you may grow a business through more customers in a current market or moving to a new market.  Therefore, your mileage may vary based on your focus.

Buyer Beware

The most significant challenge in finding an organizational or technical fit is determining where it will not be suitable.  Thus, the focus is often on where a fit occurs rather than where it does not.  That is part of the nature of selling products or convincing ourselves which solution is best.  Therefore, focus on where needs are met rather than where requirements are not.  This approach will expose solutions that do not fit.

 

Rob Broadhead

Rob is a founder of, and frequent contributor to, Develpreneur. This includes the Building Better Developers podcast. He is also a longtime student of technology as a developer, designer, and manager of software solutions. Rob is a founder and principle of RB Consulting and has managed to author a book about his family experiences. In his free time, he stays busy raising five children (although a few have grown into adults). When he has a chance to breathe, he is on the ice playing hockey to relax.

Leave a Reply