Know-Why & Know-How: What You Need to Know

  1. strategic advantage

Regardless of the business you find yourself in, two key ingredients to success are “know-why” and “know-how”. Both factors play into one another and are critical to success in terms of C-level executives down to IT generalists on staff. In this quick blog, we are going to touch on the meaning of “know-why” and “know-how”, how they impact daily/monthly/yearly strategic goals and how the successful integration of both concepts will power your IT plans to power your overall strategic advantage across the market.

The Underlying Phenomena of Know-Why

Think of “know-why” as the 30,000 foot view of any issue. The “know-why” concept is the ability to understand an underlying process and how that process helps you build your advantage across the market. “Know-why” is the ability to look at a problem in full, understand every element of how that problem arose and every element of how you solve that problem to ensure your place of growth in the market.

In short terms, “know-why” is the conceptualization of an issue, not the physical infrastructure.

The Guts of Know-How

If “know-why” is the eagles eye view of an issue, “know-how” is understanding the guts which makes up that problem. “Know-how” is understanding the day-to-day processes which makes up an overall process and how ground level actors can interact with those day-to-day processes to empower overall high level strategic goals. If “know-why” relates to C-level, VP’s and company directors, “know-how” applies directly to admins, writer, networking professionals and IT generalists.

In short terms, “know-how” is the day-in and day-out physicality of a process, not the conceptual overall meaning it holds.

Scoring the Goal Impact of Know-Why

It should come as no surprise that both “know-why” and “know-how” are critical to the overall success of your business. It should be mentioned though, both play a different role in helping your company reach differing goals yet both are key to reaching those overall and day-to-day goals.

Concerning “know-why”, the basic outlay of understanding and working through an overall process to hit company wide goals entails C-level executives working in lock step with high level business managers to develop business objectives, goals and overall strategy on how to accomplish benchmarks.

Most importantly, set benchmarks from a “know-why” standpoint must come from analytic insights. While the first step of “know-why” is understanding an overall process, the nitty gritty to building long term strategy is for higher level executives to utilize hard earned sales/marketing analytics to determine overall future strategy. More than anything else, high level executives have to make sure the data they make use of isn’t sourced from a single silo within the business but rather from business wide returns.

For a full eagles eye “know-why” strategy to emerge, business wide analytics shared between high level executives must be put to use to develop future strategy designed to lead “know-how” day-to-day work.

Scoring the Goal Impact of Know-How

As mentioned, “know-how” teams are the daily workers on the ground who have an intimate knowledge of:

  • How to deploy software, solutions and infrastructure
  • How to implement those deployments into the overall data structure of a business
  • How to utilize deployments to reach the overall strategic goals set by management

While more attention might be paid to determining overall business strategy, the true work of the company comes from the “know-how” level of implementation. It can’t be stressed enough: while setting goals from the top-down is needed for corporate guidance, those goals would never be met without the daily application of IT generalists and admins troubleshooting issues, implementing pro-active cost cutting measures and meeting deadlines well before defined ETA.

Crossing Workloads to Build Overall Strategic Power within the Market

From this quick discussion two facts can be pulled:

  • Both “know-why” and “know-how” mind sets are needed to accomplish any strategic daily/weekly/monthly/yearly goals.
  • Both “know-why” and “know-how” processes, while covering different aspects of business operations, are mutually important to one another. As “know-why” guides governing policy, “know-how” implements and provides top level analytics closing the loop and restarting the process.

Successful companies, IT centric or not, build strategic power within their market space by effectively communicating messaging and goals from top down to allow bottom up employees to carry through on daily tasks, which, in turn, informs and recalculates the entire process.

Goals = Strategic Plans = Daily Implementation = Analytic Data Sets = Changing Goals

The process, as they say, is cyclical.

To learn more download our white paper and get an in-depth look at the organizational structure of a community bank, the roles, and the skill sets you need to put in place in order to successfully implement a customer analytics project

The next step in the integration of know-why and know-how processes is best practices. In our next blog post, we will cover the best practices for full integration of the aforementioned.

If you have any questions or concerns regarding this topic or how HOSTING can help your business, feel free to contact us.

Leave a Reply

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