Freeware

This version of the NtK Model is a guide for the creation and deployment of a project output (a defined solution to a defined problem), in the form of freely available computer code or instructions, not intended for mass production and distribution in the commercial marketplace. The problem and solution set are defined in the context of an underlying need as defined by the target group which is intended to benefit from features/functions of project output. These targeted consumers/customers must be involved from the beginning and throughout the process.

Definition: The "free" in Freeware means there is no or low cost to cost to acquire the ware (product or service). Freeware encompasses both operational software applications (Apps) and user instruction kits (DIY). There are three categories of Apps: 1. Free, 2. Low Fee, 3. Freemium; and two DIY categories: 4. Free DIY, 5. Fee DIY. The Freeware category excludes outputs requiring the exchange of tangible materials.  

The NtK Model for Freeware contains Stages, Steps and Gates that may vary across the five sub-categories, as described in the five columns below.

Freeware Fee App Freemium Free DIY Fee DIY/Training
Free apps  Low cost or <$5.00 apps  Freemium cost > $5 apps Free DIY instructions to build a device Paid at single $29.95 payment, or $4.95/month recurring cost.

PHASE I — Discovery

Generating Conceptual Discoveries through Scientific and Market Research Methodologies

The Discovery Phase (Activity Stages and Decision Gates 1 through 3) necessarily begins with the conduct of primary and secondary market research activity to validate an unmet need of end users (e.g., persons with disabilities), and to define the need in the context of a problem amenable to a technology-based solution (Stage & Gate 1). The next task (Stage & Gate 2) is to assess the feasibility of deploying some envisioned product interventions as a solution to the defined problem. After the problem and solution are both defined and validated, the Scientific Research methodology may then be applied as necessary (Stage & Gate 3) to fill in any critical knowledge gaps with new-to-the-world findings. The Discovery Phase compiles knowledge from market, business, and technical analyses, scoping reviews of existing scholarly literature, along with or findings from original scientific research studies. The problem and solution set are defined in the context of an underlying need as defined by the target group which is intended to benefit from features/functions of project output. These targeted consumers/customers must be involved from the beginning and throughout the process.

Stages and Gates 1 through 3

Research

Learn More

Define Problem and Solution: Define the problem from the perspective of the eventual target consumer. Then describe the solution in objective "new to world"  terms, not subjective "new to me/us"  terms. The problem/solution set may represent an improvement in the features/functions of current market offerings, or it may represent an entirely new category of feature/function enabled by some new technological capability.

*NOTE:  Any "R&D" proposal that does not include evidence of a rigorous Stage 1 & Stage 2 should be rejected because it is driven by subjective opinions rather than objective facts. An individuals bright idea is likely subjective and insufficient justification for a new project.

Decision Gate 1

Does the proposed problem/solution set appear to be novel in state of practice; generally feasible to implement; will envisioned output be useful to target audience; and is there a clear path from project output to the beneficiary stakeholders? 

The project leader has three options:

  1. Proceed directly to Stage 2;
  2. Reiterate Stage 1 if any of the critical elements are not fully validated; or
  3. Terminate the project due to inability to clearly articulate critical elements including: Problem, Solution, Target Audience, Project Path, or Intended Output.

Activity Stage 2

Project Scoping: Conduct intensive screen to validate novelty, feasibility and utility of envisioned project to commercial partner and within the competitive marketplace.

Decision Gate 2

Does the proposed solution and path to output/outcome seem feasible to implement and accomplish? The project leader must decide now if envisioned project output and path to eventual product outcomes are still considered innovative (i.e., novel, feasible, useful) in light of results from objective value valuability assessments and SLOT analysis. A decision to continue initiates Stage 3 Research which requires secondary research to identify all knowledge relevant to project, and as necessary primary research to generate new to the world knowledge not available through existing literature or expertise. 

Activity Stage 3

Research: Conduct Secondary Archival Research to identify, acquire, translate, absorb, and apply existing science-based knowledge from qualified sources. Then, if and as necessary, conduct Primary Scientific Research to generate required new conceptual discoveries.  

Decision Gate 3

Is the Project Team qualified to puruse the downstream requirements? If so, are they prepared to commit the time and effort necessary to complete the downstream requirements for the Invention Phase and Innovation Phase? If not the team lacks the required expertise, commitment or prior commitment, what lessons can be drawn from completed work and shared with others qualified to continue?  Determine if the Discovery Phase reaffirmed the potential for the envisioned solution to address the validated problem. If so, either continue project into the Invention Phase (Stages 4 — 6), or identify appropriate partner to initiate those activities. If neither option is viable terminate project and implement Knowledge Translation Opportunity to effectively communicate the project's Conceptual Discovery to all relevant stakeholders. 

Knowledge Translation Opportunity

Whether or not project continues initiate knowledge translation activities to ensure the knowledge output created through this Phase is shared with all potential users, while taking care to protect Intellectual Property. This ensures that the time, money and effort expended — and project outputs generated to this point — have some chance of being put into practice by other stakeholders. The Knowledge to Action (KTA) diagram and table provide more detail for tailoring and targeting the project outputs to effectively communicate them to external knowledge users.  

PHASE II — Development

The Development Phase (Stages & Gates 4 — 5) involves transforming Conceptual Discoveries about validated Problems and feasible Solutions, into working prototypes of the envisioned Instrument or Tool, by rigorously applying the appropriate engineering development methods to the iterative design, construction, testing and revision to address all specified requirements. 

Stages and Gates 4 through 5

Development

Learn More

Activity Stage 4

Begin Development Effort: Build business case for commercial product & establish development plan based on established engineering methods.

Decision Gate 4

Should the development plan be implemented? Determine if all elements of the business case have been fully vetted and validated. If yes, continue on to Stage 5. If no, either terminate project or reiterate Stage 4. 

Activity Stage 5

Implement engineering development plan to build, test and refine alpha prototype for Freeware hardware or software.

Decision Gate 5

Should the project continue and go to beta prototype testing? Determine if the beta prototype will solve the problem and is feasible to deploy in the marketplace. Does it demonstrate sufficient value — efficacy/effectiveness/economies — according to the preliminary assessments in Phase I? If yes, continue to Stage 6. If no, terminate or reiterate Stage 5. 

Knowledge Translation Opportunity

For Prototype Invention Outputs

Whether or not project continues, initiate Knowledge Translation activities to ensure the knowledge output created through this Phase is shared with all potential users (i.e. potential product consumers; or intermediary stakeholders such as a Tech Transfer Office or manufacturer). This assumes that proper safeguards are in place for any proprietary information (Step 4.4). The KT activity ensures that the public funding expended and the project outputs generated have some chance of being put into practice by other stakeholders. The Knowledge to Action (KTA) diagram and table provide more detail reaching external knowledge user groups.

PHASE III — Industrial Production

The Production Phase (Stage and Gate 6) requires a shift to the application of Industrial Production methodology.

Activities include planning for all aspects of production — from manufacturing processes through after-sales service — and the execution of activities related to test marketing, launch, and on-going monitoring of the product and market conditions. Project leaders and partners need to ensure participants have the appropriate skill sets and experience to implement all of these required activities. The Production Phase output is new knowledge in the state of a Commercial Innovation deployed in the marketplace.

Stage and Gate 6

Production

Stage 6

Activity Stage 6

Beta Testing: Generate final form of Software application through iterative testing and validation.

Decision Gate 6

Should the project continue and go to Production Planning?  Continue offering and supporting Freeware?

KTA for Projects terminated prior to Production and Launch

Knowledge Translation Opportunity — for Unlaunched Innovation Outputs: If the decision is to not launch the innovation into the marketplace, then the innovation phase ends at Stage 6. Pursue this final opportunity to initiate Knowledge Translation activities to ensure the knowledge created in the state of a commercial innovation is shared with all potential users. This ensures that the resources expended and outputs generated have some chance of being put into practice by other stakeholders. The KTA Diagram for Unlaunched Innovation Outputs (552 KB) will provide more detail for tailoring and targeting the project outputs to effectively communicate them to external stakeholders.