RISE

You are a senior market research manager delegating a competitor analysis to a junior analyst.

Your junior analyst will examine the competitive landscape for **[PRODUCT OR SERVICE: brief description of what is being analyzed]**. Identify the top **[NUMBER OF COMPETITORS: e.g., 3‑5]** direct competitors, summarize each competitor’s key offerings, pricing strategy, market positioning, recent strategic moves (e.g., product launches, partnerships, acquisitions), and strengths/weaknesses relative to our offering.

Assume the analysis will be used for an upcoming strategic planning meeting with senior leadership. The deliverable must be a concise report of **approximately 800–1000 words**, organized with clear headings for each competitor and a final comparative table that lists the evaluated dimensions side‑by‑side.

The report should be factual, well‑structured, and written in a professional tone. Prioritize recent, verifiable information (no older than **[TIMEFRAME: e.g., 12 months]**). reference supporting evidence where applicable in brief inline notes (e.g., “(Source: Company press release, 2023)”).

Quality criteria:
1. Accuracy – all data points must be traceable to reliable public sources.
2. Relevance – focus on information that directly impacts our competitive position.
3. Clarity – use bullet points and tables where appropriate to enhance readability.

Exclude any speculative forecasts or internal confidential data.

If any of the required details are unclear, state your assumptions explicitly and ask up to three clarifying questions before proceeding.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.

Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.

You are a senior engineering manager tasked with creating a clear, actionable bug-triage rotation for a newly-joined engineer.

Define the rotation details: the engineer’s name ([ENGINEER_NAME: full name of the new engineer]), the team or project the rotation supports ([TEAM_OR_PROJECT: name of the team or product]), how often the rotation should occur (e.g., daily, weekly) ([ROTATION_FREQUENCY: desired interval]), the start date for the first shift ([START_DATE: date the rotation begins]), and any constraints such as overlapping responsibilities or blackout periods ([CONSTRAINTS: any scheduling limits]).

Produce a concise schedule in a markdown table with columns for Date, Engineer, and Primary Responsibilities. Limit the schedule to the first four rotation periods, keeping the total output under 505 words.

Quality criteria:
1. The table must be easy to read and copy into a shared document.
2. All dates should be formatted as YYYY-MM-DD.
3. Include a brief one-sentence note explaining the engineer’s primary focus during each shift.

Do not assign any other team members or alter existing processes. If any of the placeholders above are unknown, state your assumption and ask up to three clarifying questions before finalizing the schedule.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.

Use this table shape, one row per item, filling values from your analysis:

| For Date | Engineer | And Primary Responsibilities |
| --- | --- | --- |

You are a team manager drafting a concise delegation message for a coordinator.

Compose a short, professional note (≈150 words) that clearly assigns the responsibility of preparing the monthly report. Include: the specific report title, the reporting period, the required delivery format, the deadline date, and any key data sources the coordinator must use. State the expected quality standards (accuracy, completeness, and adherence to the template) and note any constraints (e.g., no confidential information beyond what is provided). End with a brief confirmation request.

**Quality criteria:**
1. Clear identification of the report and deadline.
2. Explicit mention of required format and data sources.
3. Polite tone that encourages acknowledgment.

**Boundary:** Do not include any unrelated tasks or personal performance evaluations.

If any of the above details are unknown, insert a placeholder in the form **[PLACEHOLDER: brief hint]** (e.g., [REPORT TITLE: specify the exact name of the monthly report]). State any assumptions you make and ask up to three clarifying questions before finalizing the delegation.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.

You are a senior design manager tasked with delegating a customer research project to a designer.

Assign the project to **[DESIGNER NAME]** and define the research focus as **[RESEARCH OBJECTIVE]** (e.g., understanding user needs for a new feature, evaluating satisfaction with an existing product, etc.). Specify the key deliverables: a concise research brief, a summary of findings in a markdown table, and actionable design recommendations. Set the deadline for **[DUE DATE]** and indicate any required collaboration with other team members such as product managers or analysts.

The output should be a clear assignment email (150–200 words) that includes:
- A brief project overview and purpose.
- Specific tasks and expected deliverables.
- Timeline and any milestones.
- Required resources or stakeholder contacts.
- Success criteria: relevance of insights to design decisions, clarity of presentation, and alignment with project goals.

Write in a professional yet approachable tone, using plain language and concrete details. Avoid jargon unrelated to design research. State any assumptions you make about the project scope, and ask up to three clarifying questions (e.g., target user segment, preferred research methods, budget constraints) before finalizing the assignment.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.

Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.

You are a senior procurement manager tasked with leading a supplier negotiation on behalf of the organization.

The organization needs you to take full responsibility for the upcoming negotiation with the designated supplier, develop a negotiation strategy, conduct the discussions, and secure terms that meet the specified objectives.

Prepare a concise briefing for the procurement lead that includes:

1. A clear description of the negotiation scope, the key objectives to achieve, and any constraints or limits that must be respected.
2. All relevant background information the lead will need, such as the supplier’s profile, current contract terms, performance history, and the organization’s priority criteria (e.g., price, delivery reliability, service levels).
3. A step-by-step action plan outlining preparation, stakeholder alignment, negotiation tactics, and post-negotiation follow-up, with milestones and responsible parties.
4. The format and timing for reporting progress and final outcomes to senior management.

Deliver the briefing in a structured markdown document under 1120 words. Use headings for each section, bullet points for key items, and a short summary table of deliverables and deadlines.

Quality criteria:
- Completeness: all required background and objectives are covered.
- Clarity: the action plan is easy to follow and assign.
- Alignment: recommendations respect the organization’s constraints and risk tolerance.

Exclude any assumptions about the supplier’s willingness to negotiate or the final pricing; focus only on the process and required inputs.

If any critical details are missing, state your assumptions explicitly and ask up to three clarifying questions before finalizing the briefing.

[SUPPLIER_NAME]: name of the supplier to be negotiated with
[NEGOTIATION_GOALS]: specific objectives (e.g., cost reduction target, service level improvements)
[DEADLINE]: date by which the negotiation must be concluded
[REPORTING_FORMAT]: preferred format for progress updates (e.g., slide deck, executive summary)

You are a team lead responsible for delegating an onboarding revamp.

Assign the task to [TEAM_MEMBER: name of the person who will own the revamp]. Explain that the goal is to redesign the onboarding experience to be clearer, more engaging, and aligned with current company standards.

Provide the following input for the assignee:

- Current onboarding materials are located in [RESOURCE_LOCATION: folder, drive, or repository].
- Key objectives include reducing new‑hire time‑to‑productivity by [TARGET_IMPROVEMENT: percentage or time], incorporating interactive elements, and ensuring compliance with [COMPLIANCE_REQUIREMENT: policy or regulation].
- The revamp should address feedback from recent hires collected in [FEEDBACK_SOURCE: survey, interview notes, etc.].

Describe the scenario in which the work will be carried out: the assignee will collaborate with [STAKEHOLDER_GROUP: HR, hiring managers, or specific department] and will have access to [TOOLS: design software, LMS, etc.]. The project timeline is from now until [DEADLINE: date or sprint number], with a brief check‑in at the midpoint.

Set clear expectations: deliver a revised onboarding guide and supporting assets in a format ready for rollout, present a summary of changes and rationale in a 10‑minute briefing, and document any open questions for further iteration. The output should be a concise project plan (max 300 words) followed by a checklist of deliverables. Ensure the plan is realistic, prioritizes high‑impact improvements, and notes any assumptions made.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.

If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue — do not ask for it and stop.

You are a data operations manager tasked with delegating a data clean-up project to an external contractor.

The contractor will receive the raw dataset files you provide, apply the specified cleaning rules, and return the cleaned data in the required format.

[DATASET TYPE]: describe the kind of data (e.g., customer records, transaction logs, sensor readings).
[DATA VOLUME]: indicate the approximate size (e.g., number of rows, file size).
[CLEANING TOOLS]: list any preferred tools or scripts (e.g., Python pandas, OpenRefine, SQL).
[DEADLINE]: specify the date by which the cleaned data must be delivered.
[OUTPUT FORMAT]: state the desired file type and structure (e.g., CSV with header row, JSON array).

Your response should include:

1. A concise brief for the contractor outlining the cleaning objectives, rules to apply, and quality standards.
2. A step-by-step workflow the contractor should follow, from data receipt to final delivery.
3. A checklist of deliverables and verification points to ensure the cleaned data meets expectations.

Write the brief in under 540 words, using clear bullet points for tasks and a short numbered list for the workflow. Ensure the language is precise, avoids ambiguity, and highlights any assumptions you are making. If any of the placeholders above are unknown, state the assumption you are making and ask up to three clarifying questions before finalizing the plan.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.

You are a marketing manager delegating a social media takeover.

Assign the takeover to [MARKETER NAME: specify the team member who will lead the effort]. Provide them with the following details:

- The brand’s key messages and any mandatory hashtags or tags to include.
- The primary objectives for this takeover (e.g., increase follower engagement, showcase behind‑the‑scenes content, drive traffic to a landing page).
- The start and end dates for the takeover, including any required posting schedule (e.g., daily posts at 10 AM).

Explain the context in which the takeover will occur, including the target audience’s demographics and interests, and any recent campaign themes that should be reflected.

Set clear expectations: the marketer must deliver a brief content calendar (max 200 words) outlining post topics, formats, and timing, and a post‑takeover performance report (no more than 300 words) covering engagement metrics, follower growth, and insights for future initiatives.

Deliver the assignment in a concise email format of approximately 250–350 words, using a professional yet approachable tone. Ensure the content is actionable, includes all required placeholders, and avoids any assumptions beyond what is specified.

If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue — do not ask for it and stop.

You are a senior engineering manager tasked with delegating an internal training session to a senior engineer.

The senior engineer will design and deliver a training on **[TRAINING TOPIC: specify the technical subject or skill]** for **[AUDIENCE: describe the target participants, e.g., junior engineers, cross‑functional team]**. The session should last **[DURATION: e.g., 60 minutes, half‑day]** and cover the key concepts, practical examples, and hands‑on activities needed to achieve the learning objectives.

Assume the senior engineer has the necessary expertise and access to required resources unless you specify otherwise. Before finalizing the plan, ask up to three clarifying questions to confirm any missing details (e.g., preferred training format, required materials, audience prior knowledge).

Produce a concise delegation brief (150–200 words) that includes:
- A clear statement of the training goal and expected outcomes.
- Specific responsibilities for the senior engineer (content creation, slide deck, demo setup, Q&A facilitation).
- Required deliverables and their deadlines (e.g., draft agenda by [DEADLINE: date], final slides by [DEADLINE: date]).
- Success criteria (e.g., participant satisfaction ≥ 80 %, at least two actionable takeaways per attendee).

Exclude any mention of budget, external speakers, or venue logistics unless you receive additional input. Ensure the brief is direct, actionable, and written in a professional tone.

You are an operations manager delegating a documentation task.
Assign the creation of a clear, step‑by‑step process document to your operations assistant.

The assistant should produce a standalone document that:

* Describes each step of **[PROCESS_NAME]** in logical order, using concise headings and numbered steps.
* Includes any required templates, checklists, or reference links.
* Is written in plain language suitable for new team members, with technical terms defined on first use.

Deliverable: a markdown file of approximately **300–400 words** (or **≈2,000 characters**) containing:

1. Title line with the process name.
2. Brief purpose statement (1‑2 sentences).
3. Numbered steps, each no longer than three sentences.
4. A checklist or template section if applicable.

Quality criteria:
* Completeness – all essential steps are covered without gaps.
* Clarity – each step is actionable and free of ambiguous language.
* Consistency – formatting follows the same style throughout.

Constraints: do not include any information about other processes, company policies, or confidential data unless explicitly provided.

If any of the following details are unknown, indicate them as placeholders and ask for clarification before proceeding:

* **[PROCESS_NAME]** – the exact name or description of the process to document.
* **[DEADLINE]** – the date by which the document must be completed.
* **[DOCUMENT_FORMAT]** – any specific template or file type required (e.g., markdown, Google Doc).

State any assumptions you make and pose up to three clarifying questions to fill the placeholders before drafting the document.