MODE: Standalone Restructuring situation: merge two production departments into one within four months while maintaining on-time order shipping 🔍 Auto-detected: Priority axes R2 Target Design, R4 Roles and Accountability, R5 People Impact and Communication, R8 Customer and Service Continuity, R10 Sequencing and Pace, target gaps R2 Target Design, R4 Roles and Accountability, R5 People Impact and Communication, R8 Customer and Service Continuity, Restructuring Scope≈2, Change Readiness≈1 (based on: the target structure, reporting lines, staff communication, and continuity approach are undefined; the change is limited to two departments but nothing has been communicated yet) — override anything above by specifying it manually in your brief. TOP-3 DIRECTIONS: 1️⃣ R2 Target Design + R4 Roles and Accountability + R5 People Impact and Communication + R8 Customer and Service Continuity + R10 Sequencing and Pace (k=5) — integrates design, people, continuity, and timing 🟢 BEST-FIT — READY-TO-USE PROMPT BELOW Target Set covered: Yes; Compatibility: Compatible — R4 and R10 naturally fit a limited-scope, early-readiness change Core: R2 Target Design + R4 Roles and Accountability; Weak link: R5 People Impact and Communication + R8 Customer and Service Continuity 2️⃣ R2 Target Design + R4 Roles and Accountability + R5 People Impact and Communication + R8 Customer and Service Continuity + R6 Talent and Knowledge Retention + R7 Process and System Alignment (k=6) — protects knowledge while aligning work and systems Target Set covered: Yes; Compatibility: Partial — R7 and R6 need adaptation for very early change readiness 3️⃣ R2 Target Design + R4 Roles and Accountability + R5 People Impact and Communication + R8 Customer and Service Continuity + R1 Case for Change + R9 Cost and Resource Logic (k=6) — clarifies rationale and resource logic alongside redesign Target Set covered: Yes; Compatibility: Partial — R1 and R9 fit scope but need adaptation to low readiness ──────────────────── 🟢 READY-TO-USE PROMPT (based on 1️⃣): Help me structure a four-month planning process for merging two production departments into one while protecting ongoing order fulfillment. Treat this as a discussion aid, not as a decision-making authority. Do not give legal, employment-law, tax, regulatory, or safety conclusions, predict savings or other outcomes, or decide which structure or option should be chosen. Those questions belong to the decision-maker and qualified professionals. Use roles rather than names and ranges rather than exact figures where possible. ✏️[COMPANY_INDUSTRY] This marker identifies the company industry needed to frame production, staffing, and continuity questions appropriately. Situation: the company has about 60 employees and plans to merge two production departments over four months. The current structure, reporting lines, communication approach, and transition design have not yet been defined. The plant must continue shipping orders on time. Use these facts as the starting point and ask for missing company-specific information rather than inventing it. Compare practical restructuring approaches that fit the five focus areas below. Consider a phased wave approach, a pilot or controlled transition, role mapping before implementation, and a structured communication plan. Compare their sequencing, information needs, decision points, operational dependencies, and discussion questions. Do not forecast savings, productivity, service results, or other outcomes. Do not select the preferred approach for the user. R2 Target Design readiness check: Work with me to define the minimum viable future-state structure before implementation. Identify the functions that will be combined, the major responsibilities of the merged department, proposed layers or teams, and unresolved design choices. Distinguish confirmed facts from working hypotheses. Do not decide the structure for me. Ask what information would be needed to compare alternative structures fairly. R4 Roles and Accountability readiness check: Work with me to map key responsibilities, reporting relationships, decision rights, escalation paths, and ownership gaps. Identify overlaps and unowned work without deciding which named person should receive a role. Use role descriptions rather than individual names. Flag any role allocation question that should be reviewed by the appropriate decision-maker or adviser. R5 People Impact and Communication readiness check: Work with me to identify which employee groups, supervisors, and other stakeholders may be affected and what each group needs to know at each stage. Build a communication sequence that distinguishes confirmed information from proposals. Do not make employment-law conclusions, prescribe legally required notices, or decide individual personnel actions. Questions involving employee rights, consultation, selection, or other employment matters should be taken to a qualified employment or legal adviser. R8 Customer and Service Continuity readiness check: Work with me to identify critical production flows, order commitments, bottlenecks, handoffs, coverage requirements, and operational constraints that could be affected during the transition. Define practical monitoring points for shipping continuity. Do not forecast service performance or promise that continuity will be maintained. Flag information that requires validation by the operations team. R10 Sequencing and Pace readiness check: Work with me to divide the four-month period into manageable stages with explicit prerequisites, owners by role, review points, and go or no-go gates. Compare a phased transition, a limited pilot, and a more direct transition without predicting which will succeed. Identify where the available time, staffing capacity, or operational demands create a tension that requires a management decision. Build a staged sequence. Stage 1 should establish the case for change, information baseline, constraints, and decision governance. Stage 2 should develop and compare future-state structure and role options. Stage 3 should prepare communication, operational safeguards, and transition dependencies. Stage 4 should use an agreed implementation approach with review points. Each stage must have a clear go or no-go gate based on evidence available at that point. A gate may pause, revise, or proceed; do not assume that proceeding is the correct choice. At each gate, identify what must be known, what remains uncertain, who has authority to decide, and what evidence should be reviewed. Do not invent figures, staffing levels, production volumes, service thresholds, dates beyond the stated four-month window, or other company-specific facts. Include questions for an employment or legal adviser about applicable employment obligations, consultation or notice requirements, documentation, and individual-impact processes. Include questions for a financial adviser about cost assumptions, transition resources, financial controls, and how proposed resource changes should be evaluated without forecasting savings. Include questions for an operations specialist about production capacity, bottlenecks, work instructions, staffing coverage, equipment dependencies, quality controls, and order-shipping continuity. List risks tied to the five focus areas, including unclear design, unresolved accountability, poor communication, disruption to production or shipping, and an unrealistic transition pace. For each risk, specify a revisit or stop point and the evidence that should trigger review. Do not assign probabilities or forecast outcomes unless the user supplies a defensible basis. For the first 30 days, or until the relevant decision date if earlier, provide a concise next-steps list covering information gathering, role mapping, future-state design work, stakeholder communication preparation, operational continuity checks, adviser questions, and the first go or no-go gate. Keep actions role-based rather than assigning decisions to named individuals. Mark every assumption explicitly. Never invent figures or company facts. Ask clarifying questions when a missing fact could materially change the analysis. Treat all proposed structures and approaches as options for discussion rather than recommendations. Do not decide who should be laid off, promoted, transferred, retained, or otherwise moved. Do not provide legal, employment-law, tax, regulatory, or safety conclusions, and do not forecast savings, returns, service levels, productivity, or other outcomes. Treat the output as a discussion aid rather than professional advice.Negative prompt / avoid: invented company facts, individual personnel decisions, unsupported savings forecasts, legal conclusions, employment-law conclusions, premature structure selection, vague reporting lines, untested continuity assumptions, big-bang implementation without gates ──────────────────── ℹ️ "This tool compares restructuring directions and builds a discussion prompt; it does not make the decision for you, give legal, employment, or financial advice, or predict savings or how a restructuring will turn out." Assumptions made: - COMPANY_INDUSTRY: the exact manufacturing industry was not provided, so the prompt marks it for clarification because production constraints and continuity questions depend on the industry. ❓ Want a different direction? Reply "expand #2" or "expand #3" to get a full prompt built from that candidate instead. 💡 Want to take this further? All three tools below are built for Claude. - Not sure your brief is ready? Search "Universal Query Auditors" on PromptBase to audit and rewrite your request before comparing directions. - Have a clear brief already and just want one direct prompt? Search "Universal Instruction Generator" for a single-pass generator. - Got a finished prompt and want it reviewed? Search "Universal Instruction Auditors" to check it against a full quality checklist before use. ⚙️ "Built for ChatGPT; other AI models, providers, and versions are untested. Use at your own discretion. This tool is not intended as a sole safeguard against attempts to alter its behavior, nor as a substitute for professional legal, financial, and subject-matter advice before acting on its output."