Time to Rebuild or Time to Build?

Some of you have heard me say that in my opinion teams should never be rebuilding but rather they should always be building. I have also said that for a team to say they need to rebuild is an admission of a failed process that has no architectural player vision.

Let’s look at this from a technology perspective. Large companies are now moving their information technology infrastructure into third party data centers in an effort to consolidate, and move data to a secure cloud infrastructure where they can reap the benefits of virtualization. Manthan-Data-Center-Technology-RefreshThis process / migration could technically be called a rebuild because often companies will use this opportunity to replace old and now obsolete technologies with newer state of the art IT equipment that moves them closer to their IT goals and vision for virtualization.

To maintain your technology infrastructure and ensure peak performance with little to no downtime companies spend a lot of time building “Technology Refresh Plans”. The purpose of the tech refresh plan is to lay out a plan / architecture that supports the adoption of newer technologies to meet changing needs or to mitigate the risk of obsolescence of existing technologies. The plan simply is to always be building capability by identifying and updating technologies that are coming up for EOL/EOS (End of Life / End of Service) or will be obsolete BEFORE it becomes a problem and creates risks.

How does this apply to professional sports organizations? Sports organizations ought to have what I like to call “Personnel Refresh Plans” where the intent of the plan is to stay a top of team capabilities and identify opportunities to advance their capability and eliminate risk. To do this teams need to have their finger to the pulse of their team and its capabilities. Many teams that I have talked to feel that between their coaching staff and general managers they know what they have and they know what they need to do to get better. Without the AS IS and TO BE architecture described in my previous post I think it is quite impossible to really know what you have from what you don’t have.

How often do you think an NFL team attempts to predict what positions they will need to draft in their next draft and future drafts after that? That is an easy question to answer, its zero! Teams tend to take a wait and see attitude before planning the next round of talent needed. That would be like a large corporation waiting for technology to become obsolete, end of life or end of service before coming up with a technology refresh strategy and by that time it’s too late. They are then chasing high failure items and hardware that demonstrates reliability issues like a fireman chases fires. Obviously you can’t predict emergencies that come up that causes you to have to adjust but winning comes from sustaining your baseline. How do you establish and maintain your winning baseline? You hire Eye-Scout to build out a sustainable baseline of player’s and their capabilities so that you can better plan current, future drafts and or player acquisitions through free agency and trades.

analytic-maturity

 

To build a successful personnel strategy that is always building and never rebuilding you always need to know 2 very key bits of information.

  1. What do you currently have in player capability?
  2. What is your team vision for the type of team that you want to be?

Without knowing these 2 things you will never be able to get to where you want to be as an organization. You know the old saying right? “If you aim at nothing you will hit it every time!”

Eye-Scout has the process and methodology that is a key enabler to ensuring that organizations are always building and never rebuilding. I have said over and over that having a sound and stable architecture is critical to ensuring you have a stable organization. Think of your team like building a house. You don’t hire an architect to design a house for you that in a few years you will have to tear down and start over. You discuss and plan your needs now and your anticipated needs for the future so that the architect can design the house to sustain your needs now and in the future. When your house starts to have problems, issues, or you start to outgrow it, you don’t tear it down and “rebuild”! What do you do? You make repairs, build additions, update rooms, kitchens, bathrooms etc so why would you tear down your team and rebuild when you can and should be making repairs, upgrades, and maintaining a winning way through maintaining your baseline?

Eye-Scout’s capability architecture process:

CBP-Process-IMAGE

This Eye-Scout developed process is made up of multiple integrated architecture products, matrices, and views that describe the architectural vision from the player capability view point and the services that those capabilities support. These products and views are what is used to evaluate the player capability gaps, needs, and are used to develop get well plans through either acquisition or player development.

DoDAF1

The Eye-Scout architectures are built in a DoDAF (Department of Defense Architecture Framework) DM2 (Department of Defense Meta-Model) compliant tool and is able to support simulations, game planning, and data analysis by the team’s technology group.

Eye-Scout works hand in hand with and in support of the team’s technology group under close supervision of the IT / Technology director and Eye-Scout senior leadership.

 

 

Leave a Reply

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