[The 9-HI™ Basics] What is 9-HI™ and what are its Use Cases?

"9-HI™ drives growth and success."

Follow this link for more details: 9-HI Introduction Presentation, or for Use Cases scroll to the bottom of this page.

9-HI™ is like a new GPS system that can guide you to technology and innovation success.
90% of all technology innovation fails in what is referred to as the "Valley of Death"
9-HI™ will help you create a map through the "Valley of Death" by identifying key Risks and ways to reduce those Risks regardless of the technology, innovation, or application.

9-HI™ is a software platform that offers a novel and highly organized way to look at technology investment, development and deployment. 9-HI™ is compatible with any technology at any Technology Readiness Level (TRL) for any application that you might want to evaluate. The 9-HI™ Process is comprehensive, holistic, and can consider everything (every opportunity and every Risk) that your team needs to consider for a successful project.

The objective of 9-HI™ is to provide comprehensive decision guidance to a team of collaborating Subject Matter Expert (SME) users so they can make better decisions and have more successful technology outcomes from investments. The process leverages the 9-HI™ 2-Tier Powerset and Artificial Intelligence (AI) to convert Subjective Information into Objective Guidance, and Qualitative Opinions into Quantitative Decisions.

The 9-HI™ process leverages a 2-Tier Powerset and Artificial Intelligence to convert subjective information into objective guidance and qualitative opinions into quantitative decisions. 9-HI™ organizes Technology Selection, Development or Deployment evaluations by these 3 Tier 1 Lanes: Product Technology, Team & Stakeholders, and Market Application. This is the Tier 1 powerset.

Each of the three Tier 1 Lanes is further defined by it's own constituent powerset otherwise called the Tier 2 Fundamental Prime Metrics (FPMs). These 9 FPM labels NEVER change regardless of what technology is developed or sought or what application is targeted for deployment.

9-HI was developed as an intelligent way of developing a (X) Product Technology through use of the (Y) Team & Stakeholders to meet the (Z) Market Application opportunity, or simply "Taking your Product to Market". However users quickly identified 15 other use cases that can be executed at any stage throughout a product or service Life Cycle:

Problem capture/topic requirements generation (including risk identification)
Conversion of goals and objectives to Success Factors (SFs)
Solution Discovery
Evidence-based solution development/deployment

Those with a “*” are use cases that may be “already underway” when initial 9-HI analysis is started. Almost one half of the total use cases are initiated while the activity is “already underway” vs a new start Project.

A. Technology solution review for application problems: This is a great activity to do before a formal acquisition or development activity takes place. It can be run as an IE project with multiple competing technology options as topics.

B. Expansion of technology/product family for new applications: This has the opposite flow of the above use case and is where a group wants to evaluate and decide how a technology or product or family of similar products can be applied to multiple applications or adjacent market segments. This kind of activity is normally done to enrich business growth or to standardize a product or technology design for improved market application volume benefits.

C. *Supply chain issues This use case evaluates a specific existing supplier or prospective supplier for Risks that exist that can result in poor supply health or reduced maturity of a supplier/ vendor. It starts off typically after an existing or potential supplier has been illuminated (ex. use of Exiger illumination technology) for potential supply issues such as Foreign Ownership (FOCI), Environmental, Social & Governance, Criminal & Regulatory, Operational, Financial, Product shipment, Cybersecurity. After analysis a complete mitigation plan can be built in the 9-HI Development module to provide guidance as the Risks are mitigated.

D. Selection or acquisition of technologies and/or suppliers This is typically used by Government organizations or medium to large enterprises. It begins with an IE project to determine potential Application, Product Technology and Team & Stakeholder Risks and Success Factors. Then Success Factors are exported through the 9-HI Wizard process to a Selection Project where the Success Factors are used as quantitative Selection/Evaluation Criteria for all proposed RFIs/RWPs/RFPs/Pitches. Down selection, to next stage or award is accomplished with SMEs and AI Agents in the 9-HI Selection Project.

E. *Evaluation and improvement of existing development projects: Start with an IE project just to confirm that the existing development project has in fact covered all of the high priority Risks that may face your project. Don’t just model what you are currently planning todo. This is where you need the AI Agents and additional human SMEs to propose addition Risks, Success Factors and Evidence needed to improve readiness and maturity right through deployment or meeting your completion TRL targets.

F. *Evaluation and improvement of current businesses and government operations: If you are managing or in leadership of a commercial business or government organization, you can use9-HI to evaluate how well your existing baseline organization is aligned to the technologies and products you have and the applications that you are involved with or intend to engage with.

G. Interest group collaboration: Typically for broad industry problems or to establish guidelines, standards, safety protocols, specifications or broad industry objectives. Ex. an engineering society may want to determine safety standards for a new technology or a group of greenfield thinkers may want to have a think tank style project that sets direction for future industry investments.

H. Investments: Similar to D, but typically these have a unique set of Risks and Success Factors for each potential company seeking investment (CSI). An IE project should be initiated by the target investment company that can be supplemented by requirements and evidence needed by the Investor. The CSI will perform a self-evaluation and provide evidence as a proposal to the investor this significantly aligns and simplifies the due diligence and funding cycle.

I. Education & Training: There are multiple Training touchpoints with 9-HI. Less experienced SMEs can be integrated into teams with seasoned SMEs to learn first-hand and grow as a SME. Also, deployment and acceptance of new technologies to customers and users as well as channel partners and other stakeholders is heavily reliant on successful education and training. More novel technologies often need education of entire sectors of customers and users before they can understand and become proficient.

J. User/customer feedback for new innovation requirements: This is a significant portion of the “Access” Fundamental Prime Metric (FPM).This feedback is dome at all lifecycle stages whether developing at medium to lower TRLs, preparing for sales or transition or well after launch or deployment in order to know when improvements are needed.

K. *Mergers & Acquisitions: After modelling your own government organization or business. You can then model potential acquisition targets to see and understand Growth from the perspectives of Risk and Reward.

L. *Business partnerships & Joint ventures: This is very similar to K above, except that after modelling is completed, the actions taken are often a subset of the actions of K.

M. Proposal opportunities: Both Solicited and unsolicited proposals are structured in a 9-HI IE project and Selection project. A proposing company can run their own 9-HI project in order to determine how well they align to a proposed customer or if they have multiple offerings, which of their offerings will best benefit the customer. Even if a proposal is unsolicited, a proposal that is quantitative and evidence based can be very powerful to win over a new customer or investor.

N. Managing system development with multiple innovations: 9-HI is structured with IE projects that can have multiple topics. If a system is being developed with multiple component developments required, it’s recommended to start with a single system level IE project and create multiple topics for each component needed development. Keep in mind that each development project only has one topic. So, the export wizard from the IE project will be used multiple times to set up a development project for each topic after the IE project has determined Risks and Success Factors.

O. *Improving manufacturing and production processes and capabilities: Many organizations rely heavily on products and technologies that are already mature and in production. Whether a technology is mechanical, chemical, electronic or software, or a combination of these, innovations of production and manufacturing should always be pursued. Quality, volume, cost reduction and efficiency are often objectives of these activities and can be modelled in an IE project with likely candidates exported to a development project for innovation and continuous improvement activities.

P. Developing services vs products: Very simply put, a service is modelled very similarly to a product in 9-HI. Users will want to evaluate whether innovative products or services can be combined to create benefits or add profits to the Group of Team and Stakeholders.