There is not a large enough market for a forms product that only offers a one-way data flow
Description
There needs to be a large enough market for a forms product that only offers a one way data flow for submissions in the early life of the product (i.e. our early proof is currently focused on digitizing existing pdf submission flows, which are by definition one-way data flows). We’re laying the groundwork for a bigger product that can enforce a consistent CX across a larger modernization effort (a “portal”, blech, etc…). We’re not planning to build a featureful two-way data flow API until we can prove value with a simpler one-way data flow. We need to segment the forms digitization/compliance market into one-way data and two-way data customers, and properly estimate the size of each. One-way customers are the lower-hanging fruit.
Source: 10x Forms Platform One Pager
Category
[ ] Timeline
[ ] Resource
[ ] Environment
[ ] Customer/Partner
[ ] Regulatory or compliance
[ ] Financial (cost/revenue)
[ ] Regulatory or compliance
[ ] Something else? Please suggest a category.
Potential Impact (1 - 10)
A quantitative rating of the potential impact on the project if the risk should materialize. Impact in a Risk Register should be scored on a scale of 1 – 10 with 10 being the highest impact.
Probability (1 - 10)
The likelihood that the risk will occur at some point in the duration of the project. This should be quantitative like Potential Impact not qualitative (high, medium or low). If you use qualitative measures you cannot calculate a Risk Score, which is done by multiplying Probability and Impact and you can easily convert a number to a descriptor e.g. 1-3 = “Low”, 4-6 = “Medium” and 7-10 = “High”.
Risk Score (Impact x Probability)
Likely Outcome
The likely consequence or impact of the risk if it materializes.
Prevention and Mitigation
Action plan to prevent a given risk from occurring, or contingency plans if the risk occurs.
Title
There is not a large enough market for a forms product that only offers a one-way data flow
Description
There needs to be a large enough market for a forms product that only offers a one way data flow for submissions in the early life of the product (i.e. our early proof is currently focused on digitizing existing pdf submission flows, which are by definition one-way data flows). We’re laying the groundwork for a bigger product that can enforce a consistent CX across a larger modernization effort (a “portal”, blech, etc…). We’re not planning to build a featureful two-way data flow API until we can prove value with a simpler one-way data flow. We need to segment the forms digitization/compliance market into one-way data and two-way data customers, and properly estimate the size of each. One-way customers are the lower-hanging fruit.
Source: 10x Forms Platform One Pager
Category
Potential Impact (1 - 10)
A quantitative rating of the potential impact on the project if the risk should materialize. Impact in a Risk Register should be scored on a scale of 1 – 10 with 10 being the highest impact.
Probability (1 - 10)
The likelihood that the risk will occur at some point in the duration of the project. This should be quantitative like Potential Impact not qualitative (high, medium or low). If you use qualitative measures you cannot calculate a Risk Score, which is done by multiplying Probability and Impact and you can easily convert a number to a descriptor e.g. 1-3 = “Low”, 4-6 = “Medium” and 7-10 = “High”.
Risk Score (Impact x Probability)
Likely Outcome
The likely consequence or impact of the risk if it materializes.
Prevention and Mitigation
Action plan to prevent a given risk from occurring, or contingency plans if the risk occurs.