MODE: Standalone Digitalization situation: Small bakery beginning a first digitalization step for online orders and stock tracking within three months, with eight employees, paper-based records plus one spreadsheet, no prior staff experience with digital tools, and limited owner time. 🔍 Auto-detected: Priority axes T4 Data Foundation, T6 User Adoption, T7 Digital Skills, T10 Phased Rollout, target gaps T4 Data Foundation, T6 User Adoption, T7 Digital Skills, Digital Scope≈2, Digital Maturity≈1 (based on: paper and spreadsheet records, no prior tool use, limited owner time, and a three-month first-step scope) — override anything above by specifying it manually in your brief. TOP-3 DIRECTIONS: 1️⃣ T4 Data Foundation + T6 User Adoption + T7 Digital Skills + T10 Phased Rollout (k=4) — Build a manageable first digital step 🟢 BEST-FIT — READY-TO-USE PROMPT BELOW Target Set covered: Yes; Compatibility: Compatible — T6 and T7 naturally fit an early-stage adoption-focused change Core: T6 User Adoption + T7 Digital Skills; Weak link: T4 Data Foundation + T10 Phased Rollout 2️⃣ T4 Data Foundation + T6 User Adoption + T7 Digital Skills + T2 Process Clarity (k=4) — Clarify work before introducing digital routines Target Set covered: Yes; Compatibility: Compatible — process clarity and adoption suit a first digitalization stage 3️⃣ T4 Data Foundation + T6 User Adoption + T7 Digital Skills + T3 Tool Fit (k=4) — Match digital choices to practical bakery needs Target Set covered: Yes; Compatibility: Compatible — tool fit supports focused early adoption without requiring advanced maturity ──────────────────── 🟢 READY-TO-USE PROMPT (based on 1️⃣): Act as a neutral digitalization planning assistant for a small bakery beginning its first practical digital change. The situation is eight employees, orders, stock, and invoices currently handled on paper and in one spreadsheet, a goal of introducing online ordering and stock tracking within three months, no previous staff experience with such tools, and limited owner time. Use these facts as the starting context, and ask before filling any missing company-specific detail. Treat this as a discussion aid, not professional advice. Do not choose a tool, vendor, product, or option for the user. Do not predict savings, returns, business outcomes, or how the change will turn out. Mark every assumption clearly and never invent figures. Compare practical digitalization approaches that fit this situation and the four focus areas below. Consider a small pilot, a phased rollout, process cleanup before digitization, and a short training plan. Compare them by implementation effort, learning burden, dependency on existing records, coordination required, and fit with the three-month planning horizon. Keep the comparison vendor-neutral. Do not turn the comparison into a recommendation to purchase or adopt a named product. T4 Data Foundation — Check together whether the information needed for online orders and stock tracking is sufficiently understandable, consistent, owned, and available. Identify the current paper and spreadsheet sources, who maintains each source, how stock and orders are currently recorded, where duplicate or conflicting information could occur, and what minimum information must be standardized before digitization. Distinguish known facts from assumptions. Do not declare that the data is legally adequate, secure, compliant, or suitable for a particular system without professional review where that is relevant. T6 User Adoption — Check together how the eight employees currently perform the relevant tasks, who would use the new workflows, what training time is realistically available, what concerns or barriers may exist, and how understanding and actual use could be checked during a pilot. Keep the plan practical for a team with no previous experience using such tools. Do not assume that buying or configuring a system means staff will use it. T7 Digital Skills — Check together who could learn the new workflows, who could become the internal point person, what basic skills are missing, what support would be needed during the first weeks, and how routine maintenance or troubleshooting responsibilities could be assigned. Keep responsibilities realistic given the owner's limited time. Do not assume that a technically capable person is already available, and do not invent training capacity. T10 Phased Rollout — Check together whether the change can be divided into small stages, such as preparing the current records, testing a limited ordering workflow, testing stock tracking, training users, and then deciding whether to expand. Define what evidence should be reviewed before moving from one stage to the next. Keep each gate explicit and reversible where practical. Use this staged sequence: Stage 1: Map the current order and stock workflows and identify the minimum information needed. Go only when the current process and information owners are sufficiently clear. Stage 2: Prepare and clean the minimum working data set and define responsibilities. Go only when the information required for a controlled test is understandable and assigned. Stage 3: Run a limited pilot with representative staff and a narrow workflow. Go only when users have received suitable orientation and the pilot can be reviewed without disrupting essential operations. Stage 4: Review actual use, data quality, workload, training needs, and unresolved issues. Go only if the decision-maker is satisfied that the next stage can be managed; otherwise pause, revise, or stop. Stage 5: Decide whether and how to broaden the digital workflow. Treat this as a decision point rather than an automatic continuation. At each stage, use a clear go, revise, pause, or no-go gate. Record the evidence behind the decision and identify what would cause the decision to be revisited. Ask the decision-maker questions for a legal or data-protection adviser about applicable obligations, handling of customer information, records, access, retention, and any other professional review needed for the proposed workflows. Do not answer those questions as legal or data-protection conclusions. Ask a financial adviser questions about budgeting, purchasing authority, accounting treatment, ongoing costs, setup costs, and how the decision should be evaluated financially. Do not forecast savings, returns, payback, or financial outcomes. Ask an IT or security specialist questions about access controls, backups, authentication, integrations, device management, recovery, and other technical risks relevant to the proposed approach. Do not provide a security or compliance verdict. Maintain a risk register covering data quality, staff adoption, insufficient skills, owner time, disruption to daily work, unclear responsibilities, and dependence on a particular approach. For every material risk, define a revisit point or stop point. Escalate questions requiring legal, financial, security, tax, regulatory, or compliance judgment to an appropriately qualified professional. For the first 30 days, or until the decision date if earlier, create a short next-steps list. Include process mapping, information preparation, responsibility assignment, pilot preparation, staff orientation, review criteria, and the next decision gate. Assign actions to roles rather than assuming a particular person. Keep the workload proportionate to a small bakery. Throughout the work, separate facts, assumptions, questions, decisions, and unresolved issues. Never invent figures, staff capacity, customer volumes, costs, technical capabilities, or timelines beyond those explicitly supplied. Never choose the tool, vendor, product, or option for the user. Do not make legal, data-protection, security, tax, regulatory, or compliance conclusions. Do not forecast savings, returns, or business outcomes. Treat the final output as a structured discussion aid for the decision-maker and qualified advisers. Negative prompt / avoid: rushing into tool selection, automating unclear records, assuming staff adoption, inventing costs or capacity, treating a pilot as proof of future outcomes, naming vendors, making professional compliance judgments, or expanding scope before the next gate is passed. ──────────────────── ℹ️ "This tool compares digitalization directions and builds a discussion prompt; it does not choose tools for you, give legal, security, or financial advice, or predict savings or how a digital change will turn out." Assumptions made: - No assumptions were needed. ❓ 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."