Stress-test a roadmap against delays, capacity loss, hidden dependencies, and stale priorities, then create a practical prevention plan.
No public result for version 1 yet
Version 1 · 3 variables · 3 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
The outcome whose failure the team wants to prevent. Default: Launch a usable customer portal pilot with five customers
Time window being planned. Default: The next six weeks
Roadmap, owners, capacity, dependencies, and success criteria. Default: Week 1: Jo interviews pilot customers and drafts the invitation. Week 2: Rin adds account access. Week 3: Rin builds document upload. Week 4: Alex reviews support content and the team tests the flow. Week 5: Invite five customers. Week 6: Observe usage and collect feedback. Constraints: Rin is the only engineer; no hiring budget. Customers must sign in before uploading. Jo can spend two days per week on the pilot. Success means all five invited customers can sign in and upload one document; no retention target has been set.
Act as a project premortem facilitator. Review the plan below for Launch a usable customer portal pilot with five customers, using this planning horizon: The next six weeks.
Plan and known constraints:
Week 1: Jo interviews pilot customers and drafts the invitation. Week 2: Rin adds account access. Week 3: Rin builds document upload. Week 4: Alex reviews support content and the team tests the flow. Week 5: Invite five customers. Week 6: Observe usage and collect feedback.
Constraints: Rin is the only engineer; no hiring budget. Customers must sign in before uploading. Jo can spend two days per week on the pilot. Success means all five invited customers can sign in and upload one document; no retention target has been set.
Imagine the objective was missed. Explore plausible failure paths using these stress tests: the top priority takes twice as long; a key contributor is unavailable for six weeks; a hidden dependency blocks several tasks; work continues from habit after its value changes; and priorities solve an outdated problem. Treat these as hypothetical scenarios, not forecasts or claims about the team.
Produce a risk table with: failure scenario, specific part of the plan exposed, earliest observable warning sign, consequence, prevention step, fallback, and a proposed role to monitor it. Use high/medium/low impact with a short reason; do not invent numeric probabilities. Identify which risks are already supported by the plan and which are assumptions to validate.
Then recommend the three highest-value changes to the plan. For each, state what changes, what tradeoff it introduces, and the question or evidence needed before adopting it. Include one item to stop, defer, or simplify if the evidence supports doing so. End with a 20-minute team discussion agenda that resolves the most important unknowns.
Do not invent staffing, budget, commitments, or dependencies as established facts. Keep recommendations within the supplied constraints, flag conflicts, and ask focused questions where missing information prevents a useful judgment.No public examples yet for version 1
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Curated prompt only. No example output or model test is attached; model compatibility has not been verified. Default inputs are illustrative practice material; replace them with your own facts and context.
Reports go to moderators and are never shown publicly.
No public results yet
Plan an online session minute by minute, including speaker cues, technical preparation, audience participation and contingencies for common disruptions.
No public results yet
Apply your own expense categories consistently, preserve original transactions and flag ambiguous items, duplicates and possible recurring charges.
No public results yet
Create a practical packing list matched to trip length, activities, expected conditions, laundry access and the luggage limits you provide.
No public results yet
Turn a client conversation into a concise handoff with context, feedback, scope changes and unresolved decisions for colleagues in another time zone.
No public results yet
Surface the values behind competing priorities and prepare shared criteria, compromise options or a small experiment to resolve disagreement.
No public results yet
Prepare a scope workshop with proposed Must, Should, Could and Won’t categories, explicit tradeoffs and questions for disputed requirements.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.