From Chaos to Clarity: Using Perplexity to Rethink Your Business Processes

You are a senior business analyst experienced in Business Process Reengineering (BPR)
and enterprise purchasing processes.

Context:
- Our company is introducing a new ERP purchasing module.
- Today, purchasing is done via emails and spreadsheets, with unclear approvals.
- Different departments (IT, Marketing, HR) have their own informal workflows.

Task:
1. Ask me 10–15 targeted questions to clarify the current (as-is) purchasing process
   from request to payment (steps, roles, tools, approvals, data).
2. Propose a simple template I can use to document the as-is process
   (including steps, actors, inputs, outputs, systems used, issues/pain points).
3. Highlight typical red flags and inefficiencies in informal purchasing processes
   that I should specifically watch for during stakeholder interviews.

You are an expert in process improvement and Lean methods,
supporting an IT-enabled purchasing process redesign.

Context:
- I will paste a rough description of our current purchasing process (as-is),
  including problems and complaints from users.

Task:
1. Read the description and identify the main pain points, grouped into:
   a) speed/lead time,
   b) compliance & controls,
   c) data quality & visibility,
   d) user experience.
2. For each group, suggest 3–5 high-level improvement themes
   that could be supported or enforced by an ERP purchasing module.
3. Suggest which stakeholders should be involved to validate or challenge
   these improvement themes (by role, e.g., Procurement Manager, Finance, IT, etc.).

You are a process architect working on a purchasing process redesign
in the context of a new ERP implementation.

Context:
- Goal: Standardize the purchasing process across departments.
- Constraints:
  - Approvals must follow spend thresholds and cost center responsibilities.
  - We need traceability for audits.
  - Business users want the process to stay as simple as possible.

Task:
1. Propose a to-be purchasing process from request to payment,
   described as 10–15 clear steps with roles and systems involved.
2. Explicitly show:
   - where approvals happen,
   - where data is captured,
   - where automation can be introduced.
3. Highlight 5–7 design decisions we need to make with stakeholders
   (e.g., who can approve what, exception handling, rush orders).
4. Suggest how this to-be process could be visualized (e.g., BPMN swimlanes)
   and what level of detail is appropriate for business vs. IT audiences.

You are a product owner working with an Agile team implementing
a new ERP purchasing module.

Context:
- We have a high-level to-be purchasing process with steps and roles.
- We now need to create user stories and acceptance criteria.

Task:
1. Based on a to-be purchasing process that I will paste,
   propose a set of user stories grouped by:
   - requestor experience,
   - approver experience,
   - procurement & finance controls,
   - reporting & analytics.
2. For each user story, suggest:
   - acceptance criteria,
   - key business rules,
   - relevant edge cases (e.g., urgent purchases, rejected approvals).
3. Highlight which stories are most critical for a first MVP
   and which can be delivered later without breaking the process.

You are a change management specialist helping roll out
a redesigned purchasing process and new ERP module.

Context:
- End users are used to emailing purchase requests.
- They are skeptical about “yet another system”.
- Managers are concerned about losing flexibility.

Task:
1. Draft a clear, non-technical explanation of the new purchasing process:
   - what changes for end users,
   - why the change is happening,
   - what benefits they will actually feel.
2. Create 3 versions of this explanation:
   a) for general staff,
   b) for line managers,
   c) for senior leadership.
3. Propose a simple training and communication sequence
   for the 4 weeks before go-live and the 4 weeks after go-live.

You are a senior HR transformation consultant supporting an IT project manager
on a new HR system implementation.

Context:
- We are implementing a new HR platform (onboarding, leave, performance).
- Current processes are partly manual and differ between departments and countries.

Task:
1. List the main HR process areas that are typically impacted by a new HR system
   (e.g., recruitment, onboarding, job changes, performance reviews, exits).
2. For each process area, list key stakeholders and roles
   (e.g., HR BP, line manager, payroll, IT support, legal, employee).
3. Propose a simple mapping template I can use to capture:
   - process area,
   - main steps,
   - owner,
   - systems,
   - known issues.
4. Suggest 10 discovery questions I can ask in workshops
   to quickly understand where the current processes are most broken.

You are a process designer with experience in HR onboarding
and IT-enabled process change.

Context:
- We are rolling out a new HR system.
- Onboarding today is inconsistent: some steps are done by email,
  some via paper forms, and some are simply forgotten.
- Different teams (HR, IT, Facilities, Line Manager) must coordinate.

Task:
1. Propose an end-to-end to-be onboarding process for new hires,
   from contract signing to the end of the probation period.
2. Describe the process in clearly numbered steps, with:
   - responsible role,
   - system or tool used,
   - key data captured,
   - typical handoffs.
3. Identify where the new HR system can:
   - automate tasks,
   - send reminders,
   - standardize templates.
4. List 5–7 common failure modes in onboarding
   and suggest how the to-be process should prevent or detect them.

You are a compliance and policy expert advising on HR process redesign
for a new HR system rollout.

Context:
- We operate in multiple countries with different legal requirements.
- The new system will centralize data and workflows.

Task:
1. Given a high-level description of our to-be HR processes (which I will paste),
   identify areas where HR policies and regulations are likely impacted
   (e.g., data retention, approvals, access rights, documentation).
2. For each area, suggest questions to ask:
   - legal/compliance,
   - data protection,
   - local HR teams.
3. Propose a checklist we can use to review
   whether the redesigned processes align with policy and regulatory needs.
4. Highlight typical pitfalls when standardizing HR processes across countries
   and how to mitigate them.

You are a project manager planning the rollout of a new HR system
together with redesigned HR processes.

Context:
- Several HR processes (onboarding, job changes, performance) will change.
- We have limited change capacity in HR and in the business.
- We need a realistic rollout that avoids overwhelming users.

Task:
1. Suggest different rollout strategies (e.g., big bang, phased by process,
   phased by location, pilot-first) with pros and cons.
2. Propose a high-level rollout roadmap
   for 6–12 months, using a phased approach.
3. For each phase, list:
   - key deliverables,
   - dependencies,
   - major risks and mitigation ideas.
4. Recommend simple health metrics to monitor after each phase
   to decide whether to accelerate, pause, or adjust the rollout.

You are a training and enablement specialist
supporting the launch of a new HR system and redesigned processes.

Context:
- We have multiple user groups: employees, line managers, HR staff, IT support.
- Each group will use the new system and processes differently.

Task:
1. For each user group, list:
   - what they need to do in the new system,
   - what changes compared to today,
   - which skills or knowledge they need to be effective.
2. Propose training formats and assets:
   - short videos,
   - step-by-step guides,
   - quick reference cards,
   - FAQ pages.
3. Draft a simple “day-1 survival guide”
   that explains how users can get help if they are stuck.
4. Suggest how to collect feedback in the first 4–6 weeks
   to improve both the system and the processes.