dimension_name
stringclasses 1
value | dimension_values
listlengths 3
3
| dimension_description
stringclasses 1
value | question
stringlengths 57
104
| why_differ
stringlengths 140
256
| how_subtle
stringlengths 77
170
| sampled_value
stringclasses 3
values | num_distractors
int64 5
5
| ground_truth_persona
stringlengths 144
311
| distractor_personas
listlengths 5
5
| personalized_response
stringlengths 72
1.06k
|
|---|---|---|---|---|---|---|---|---|---|---|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Outline a plan for delivering a project status update to stakeholders next week.
|
The response would vary in structure and precision: one might focus on key wins and issues conversationally, another would emphasize business outcomes and timelines, and another would present a tightly structured brief with defined metrics and scope notes.
|
Differences appear in ordering (headlines vs KPIs first), level of quantification, and degree of hedging or exactness rather than obvious tone markers.
|
Formal
| 5
|
An analyst preparing a stakeholder-facing update who insists on precise, fully articulated language. Expects complete sentences, accurate terminology, and measured wording throughout. Values unambiguous phrasing and professional decorum.
|
[
"A team lead who likes an easygoing, conversational update. Prefers a friendly tone with contractions and simple phrasing. Appreciates plain talk over stiff wording.",
"An individual contributor who wants the status shared in a relaxed, approachable voice. Enjoys chatty summaries with clear takeaways and a light touch. Comfortable with minimal formality as long as the message is clear.",
"A project lead who favors a down-to-earth vibe. Likes updates that feel like a hallway chat—personable, straightforward, and easy to follow. Fine with informal language as long as the message stays clear.",
"A project manager who prefers a polished, business-appropriate style. Wants clear, concise explanations suitable for executives. Expects a confident, courteous voice without sounding stiff.",
"A coordinator who expects a refined, corporate-ready update. Values succinct, well-chosen wording and clear ownership. Prefers a steady, respectful tone without overly formal phrasing."
] |
To deliver a project status update to stakeholders next week, we will follow a structured approach. Firstly, we will compile a comprehensive report detailing the project\'s current progress, highlighting key milestones achieved, and outlining any challenges encountered. This report will be reviewed and finalized by the project team to ensure accuracy and completeness. Once finalized, the report will be presented to stakeholders via a scheduled meeting, allowing for open discussion and Q&A. Additionally, we will provide stakeholders with regular project updates through a dedicated project management tool, ensuring they have access to the latest information and can track progress in real-time. By following this plan, we aim to provide stakeholders with a clear understanding of the project\'s status, enabling informed decision-making and fostering a collaborative environment.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How should I ask for a two-day extension on a deliverable while maintaining credibility?
|
One approach will highlight context and a personal commitment, another will stress impact and mitigation for stakeholders, and another will foreground formal justification and accountability language.
|
Cue is in the balance of empathy, business rationale, and formal framing (e.g., explicit contingencies, precise commitments), not in overt stylistic tells.
|
Casual
| 5
|
A team contributor who likes to keep messages friendly and straightforward. Prefers quick, conversational notes with clear asks and timelines. Focused on being honest and practical without sounding stiff.
|
[
"An organized team member who drafts polished messages suitable for business settings. Emphasizes clarity, concise structure, and respectful tone while staying approachable. Seeks to maintain credibility with clear next steps.",
"A project lead who writes succinct, well-structured emails with courteous phrasing. Prioritizes transparency, accountability, and specific commitments. Aims for a confident, businesslike tone.",
"A consultant who communicates in a refined, business-appropriate manner. Uses clear subject lines, brief context, and actionable requests. Strives for a professional tone without sounding rigid.",
"An analyst who composes precise correspondence with complete sentences and formal salutations. Prefers meticulous wording, explicit justifications, and unambiguous deadlines. Maintains a high level of decorum in all written requests.",
"A researcher who writes with rigorous grammar and carefully structured paragraphs. Provides detailed rationale, cites constraints where relevant, and specifies exact dates. Keeps communication highly formal and deferential."
] |
To request a two-day extension, I suggest framing it as an opportunity to ensure the deliverable meets the expected quality standards. You could say something like,
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Propose a structure for a client discovery call to uncover goals, constraints, and success criteria.
|
One style will use open, rapport-building prompts, another will present a clear agenda tied to outcomes, and another will use precise definitions and sequencing for requirements elicitation.
|
Variation lies in the specificity of questions, the degree of agenda signposting, and use of categorization (scope, assumptions, risks) without explicit register signals.
|
Casual
| 5
|
Communicates in a friendly, conversational way and keeps wording simple and relatable. Comfortable with contractions and approachable phrasing. Prefers minimal jargon while staying focused on the client’s needs.
|
[
"Communicates with a polished, businesslike tone using clear, concise phrasing. Keeps language professional and respectful without being stiff. Uses standard business terminology when it improves clarity.",
"Uses precise, grammatically rigorous language with complete sentences throughout. Avoids contractions and colloquialisms entirely. Prefers unambiguous, formal terminology.",
"Maintains a client-facing, corporate voice that is courteous and to the point. Balances warmth with professionalism and avoids slang. Chooses precise, business-appropriate wording.",
"Maintains a consistently formal register and measured wording. Employs carefully defined terms and meticulous phrasing. Refrains from casual expressions or idioms.",
"Uses refined, executive-ready language and succinct, direct sentences. Keeps the conversation composed and respectful, avoiding colloquialisms. Incorporates professional terminology where appropriate."
] |
To uncover goals, constraints, and success criteria for a client discovery call, consider the following structure: \n\n1. Introduction (5-10 minutes): Establish rapport, explain the purpose and process of the call, and set expectations.\n\n2. Current Situation (15-30 minutes): Ask open-ended questions to understand the client's current challenges, pain points, and objectives.\n\n3. Goals and Objectives (15-30 minutes): Explore the client's desired outcomes, priorities, and non-negotiables.\n\n4. Constraints and Assumptions (10-20 minutes): Discuss any limitations, assumptions, or external factors that may impact the project.\n\n5. Success Criteria (10-20 minutes): Define measurable indicators of success and how they will be evaluated.\n\n6. Next Steps (5-10 minutes): Summarize the key takeaways, agree on the next steps, and establish a timeline for the project.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
I need to present quarterly results to leadership. How should I frame the story?
|
One framing emphasizes narrative and memorable highlights, another aligns metrics with business objectives, and another uses formal definitions, baselines, and variance analysis.
|
Perceivability comes from whether the answer privileges narrative flow, outcome alignment, or methodological rigor and exact terms.
|
Formal
| 5
|
Preparing quarterly results for senior leadership. Prefers precise, fully articulated sentences and an objective tone that uses established business terminology. Seeks guidance that reads like a formal brief, avoiding contractions and colloquialisms.
|
[
"Getting ready to walk leadership through quarterly results. Likes a friendly, conversational voice with contractions and approachable phrasing. Appreciates guidance that feels like a chat, light on jargon.",
"Preparing to share quarterly results with leaders. Wants relaxed, down-to-earth language that keeps things simple and relatable. Prefers tips phrased in everyday terms, with a warm tone.",
"About to present quarterly results to the top team. Likes an easygoing style with plain words, short, natural sentences, and a personable vibe. Open to a bit of energy in the wording, as long as it stays clear.",
"Preparing quarterly results for an executive audience. Prefers polished, business-appropriate language that is concise and direct, without sounding stiff. Wants guidance that feels executive-ready and uses clear, practical phrasing.",
"Planning a leadership presentation on quarterly results. Favors crisp, professional wording with clean structure and no slang. Seeks a confident, concise tone suitable for boardroom communication."
] |
To effectively frame the story for presenting quarterly results to leadership, focus on highlighting key performance indicators (KPIs) that demonstrate progress toward strategic objectives. Emphasize achievements, challenges, and areas for improvement, and provide actionable recommendations for future growth. Consider using visual aids such as charts and graphs to illustrate trends and data, and ensure that the narrative is concise, clear, and free of technical jargon.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Draft a plan for communicating a minor product issue that affects a subset of users.
|
One plan focuses on clarity and reassurance, another includes stakeholder mapping and next steps, and another specifies incident classification, timelines, and formal commitments.
|
Differences show up in incident taxonomy, precision of commitments, and escalation paths rather than overtly different diction.
|
Professional
| 5
|
Communicates in a polished, business-appropriate tone. Values clarity, courteous wording, and concise explanations that instill confidence. Avoids slang while staying approachable.
|
[
"Sounds like a friendly teammate in everyday conversation. Uses contractions and plain language to keep things light and approachable. Leans on a reassuring, down-to-earth voice.",
"Keeps messages relaxed and conversational, as if chatting one-on-one. Chooses simple, informal phrasing that feels relatable and warm.",
"Explains issues in straightforward, everyday terms with an easygoing tone. Comfortable keeping the message informal and personable.",
"Writes with precise, fully structured sentences and exact terminology. Avoids colloquialisms and maintains a measured, authoritative tone.",
"Employs grammatically rigorous phrasing and complete sentences throughout. Prefers elevated diction and a meticulously composed, authoritative style."
] |
We are aware of a minor product issue that affects a subset of users. Our team is working to resolve the issue as soon as possible. In the meantime, you can continue to use the product as usual, and we will notify you once the issue is fixed.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Suggest a way to give constructive feedback to a colleague whose handoffs are inconsistent.
|
One approach will lean on examples and collaborative tone, another will propose a structured framework with action items, and another will formalize observations with criteria and expected standards.
|
Signals include use of frameworks, explicit performance criteria, and documented follow-ups versus more example-led, conversational guidance.
|
Casual
| 5
|
I like to keep things friendly and straightforward. I use everyday language, examples, and quick, practical tips. I appreciate a warm, constructive tone that gets to the point.
|
[
"I maintain a clear, polished style suitable for the workplace. I prefer concise recommendations, concrete examples, and actionable next steps. A respectful, solution-focused tone is important to me.",
"I communicate with a polished, business-appropriate tone. Please provide structured guidance with succinct points and clear takeaways. I value diplomacy and clarity in wording.",
"My preference is for crisp, workplace-ready language. Keep suggestions organized, specific, and tied to outcomes. Courteous and constructive phrasing helps me act quickly.",
"I favor precise, grammatically rigorous communication in complete sentences. Provide structured guidance with explicit definitions and unambiguous recommendations. Maintain a courteous, objective tone throughout.",
"I prefer discourse that is meticulous and exact. Present information in well-formed sentences, with clear rationale and orderly steps. Avoid colloquialisms and ensure terminological consistency."
] |
To give constructive feedback, start by scheduling a private meeting with your colleague. Be specific about the inconsistent handoffs you’ve observed, focusing on the impact rather than making a personal attack. Use ‘I’ve noticed’ or ‘I’ve seen’ statements to describe the behavior, and avoid blaming language. For example, say ‘I’ve noticed that the patient’s medication list has been incomplete during handoffs on three occasions’ instead of ‘You always forget to include the medication list.’ After describing the issue, clearly state the expected behavior and provide a specific example of what you’d like to see in the future. End the conversation by reiterating your commitment to working together as a team and offering support to help your colleague improve. Remember to listen actively and respond thoughtfully to their concerns and questions.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How should I prioritize tasks for the week when everything feels important?
|
One response centers on pragmatic triage and personal bandwidth, another introduces objectives, stakeholder impact, and deadlines, and another formalizes criteria, weighting, and review cadence.
|
Differences are in choice of prioritization method (simple triage vs OKR alignment vs scoring), not overt tone or word choice.
|
Casual
| 5
|
Has a packed to-do list for the week and wants help deciding what to tackle first. Likes plain-English, friendly advice with concrete tips and quick wins—no stiff jargon.
|
[
"Has a heavy slate of tasks this week and needs a clear prioritization plan. Prefers polished, concise guidance with structured bullet points, criteria, and specific next steps.",
"Managing competing deadlines and wants a practical weekly game plan. Expects succinct, well-organized recommendations that highlight impact and effort, with a brief executive summary.",
"Balancing multiple commitments and seeks a prioritization framework for the week. Values crisp, workplace-ready communication with clear tiers, timelines, and action items.",
"Facing numerous obligations and requests a methodical explanation for prioritizing the week. Prefers precise instructions in complete sentences, with explicit definitions, criteria, and rationale.",
"Overwhelmed by competing priorities and wants a thorough, structured methodology. Values meticulous wording, unambiguous sequencing, and fully articulated reasoning."
] |
Start by identifying the most critical tasks that have deadlines or significant consequences. Then, prioritize them based on their urgency and impact. Use the Eisenhower Matrix to categorize tasks into four quadrants: urgent and important, important but not urgent, urgent but not important, and not urgent or important. Focus on the tasks in the first quadrant first, and then move on to the others. Consider breaking down large tasks into smaller, manageable chunks to make them feel less overwhelming. Finally, review your list regularly and adjust your priorities as needed.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What belongs in a one-page summary of a technical research paper for a general audience?
|
One summary emphasizes the core idea and relatable impact, another aligns findings to business or practical relevance, and another ensures precise terminology, limitations, and citations.
|
Cue emerges from inclusion of definitions, treatment of assumptions, and structured sections versus approachable framing.
|
Casual
| 5
|
Enjoys a friendly, plain-English style with contractions and a relaxed vibe. Prefers short, punchy sentences and simple explanations without jargon. Appreciates a conversational tone that feels approachable.
|
[
"Prefers a polished, businesslike tone with clear, concise sentences. Values well-organized explanations and courteous wording. Avoids slang while keeping the language approachable.",
"Leans toward a crisp, professional voice suitable for workplace communications. Expects concise phrasing, logical flow, and respectful language. Keeps the tone confident but not overly formal.",
"Favors a clean, office-ready style that reads smoothly in executive summaries. Prioritizes precise wording, brevity, and professional courtesy. Avoids casual expressions.",
"Expects rigorous, formally constructed prose with complete sentences and exact terminology. Values objectivity, precision, and adherence to standard grammar and usage. Avoids colloquialisms and conversational asides.",
"Prefers an academic, ceremonious register with explicit definitions and unambiguous statements. Emphasizes formality, technical correctness, and a measured cadence. Steers clear of idioms and informal shortcuts."
] |
A one-page summary should include the main question or problem the research is trying to solve, a brief explanation of the research method, the key findings, and a conclusion that explains the significance of the research and its potential impact.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Propose a checklist for a release notes document for a small update.
|
One checklist highlights user-facing changes and simple guidance, another adds impact, dependencies, and rollout notes, and another includes versioning, references, and formal deprecation notices.
|
Variation is in taxonomy depth, standardization (e.g., semantic versioning), and specificity, not obvious stylistic flair.
|
Formal
| 5
|
Preparing documentation for a small update. Expects precise, grammatically rigorous wording with complete sentences and standard technical terminology. Prefers a structured, professional presentation and avoids colloquialisms.
|
[
"Preparing documentation for a small update. Wants an easygoing, conversational voice with contractions and friendly phrasing. Prefers simple, approachable lines over formal wording.",
"Preparing documentation for a small update. Looks for polished, business-appropriate language that is clear and concise without sounding stiff. Values a balanced, approachable tone suited to workplace readers.",
"Preparing documentation for a small update. Favors relaxed, personable phrasing that reads like everyday speech, with minimal jargon. Keeps things light while staying clear.",
"Preparing documentation for a small update. Seeks crisp, succinct wording appropriate for workplace communication, polite and confident. Avoids slang but stays accessible.",
"Preparing documentation for a small update. Prefers friendly, down-to-earth language with contractions and straightforward sentences. No stiff or overly formal phrasing."
] |
Here is a proposed checklist for a release notes document for a small update:
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How do I prepare for a negotiation where both sides want a quick resolution?
|
One plan emphasizes rapport and simple trade-offs, another details objectives, BATNA, and concessions, and another codifies terms, scope boundaries, and documentation of outcomes.
|
Distinctiveness shows in whether the approach is relationship-first, outcome-structured, or agreement-formalized with precise definitions.
|
Casual
| 5
|
I’m getting ready for a negotiation and want straightforward, no-fluff advice. Keep it friendly and easy to read, with concrete steps I can use right away. Contractions and a conversational vibe are welcome.
|
[
"I’m preparing for a negotiation and would appreciate concise, business-appropriate guidance. Please keep the language polished and clear, with actionable steps I can apply immediately.",
"I need practical guidance for an upcoming negotiation in a work context. Use a refined, organized tone and provide specific, actionable steps.",
"I’m seeking advice I can bring into a professional meeting. Present the recommendations in a crisp, structured manner with clear, actionable takeaways.",
"I require guidance for an imminent negotiation, articulated with precise grammar and complete sentences. Please employ professional terminology where appropriate and avoid colloquialisms while outlining actionable steps.",
"Kindly provide preparation guidance suitable for a formal briefing. Use clear, unambiguous language and maintain a measured, respectful tone while presenting actionable steps."
] |
To prepare for a negotiation where both sides want a quick resolution, focus on clear communication, define the scope of the negotiation, and establish a clear understanding of the goals and constraints of both parties. Consider the following steps: 1. Identify the key issues and prioritize them. 2. Develop a clear and concise proposal that addresses the key issues. 3. Be prepared to make concessions and find creative solutions. 4. Use time pressure to your advantage by setting deadlines and encouraging the other party to make decisions quickly. 5. Be flexible and open to compromise, but also be clear about your limits. 6. Use active listening skills to ensure you understand the other party's needs and concerns. 7. Be prepared to walk away if the negotiation is not meeting your goals.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Suggest an outline for documenting a decision about deferring a feature to the next sprint.
|
One outline focuses on context and the practical reason, another ties to roadmap impact and stakeholders, and another enumerates criteria, alternatives considered, and risk assessment.
|
The cue is the presence of decision records, criteria, and traceability versus straightforward explanation.
|
Formal
| 5
|
Prefers precise, grammatically rigorous writing with complete sentences and unambiguous phrasing. Avoids colloquialisms and favors professional terminology. Expects a clearly structured document with consistently labeled sections.
|
[
"Prefers polished, business-appropriate language that is clear and concise without sounding stiff. Uses standard industry terms and straightforward headings suited for broad stakeholders.",
"Communicates in a conversational style with contractions and friendly phrasing. Comfortable with simple headings and minimal jargon to keep things approachable.",
"Values a crisp, executive-ready tone with concise sentences and clean formatting. Avoids slang while keeping language approachable and practical.",
"Likes write-ups that read like a team chat: relaxed wording, brief bullets, and plain language. Fine with informal section titles as long as the gist is clear.",
"Seeks a balanced, businesslike voice that is polished and easy to scan. Prefers clear section titles and professional wording without excessive formality."
] |
To document a decision about deferring a feature to the next sprint, consider the following outline:
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How should I announce a meeting agenda that keeps the group on time?
|
One approach stresses concise goals and time boxes, another adds objectives, owners, and expected outcomes, and another introduces formal sequencing, pre-reads, and decision protocols.
|
Perceivability lies in the granularity of roles, inputs, and outputs, not in explicit tone differences.
|
Formal
| 5
|
A meticulous communicator who favors complete sentences, precise phrasing, and courteous salutations. Prefers structured announcements with clear headings and unambiguous terminology, avoiding contractions. Seeks to keep meetings orderly and on time through explicit expectations.
|
[
"Communicates in a polished, businesslike tone with concise, courteous wording. Prefers clear bullets and actionable phrasing without slang, keeping messages succinct. Aims to set expectations to keep meetings efficient.",
"Uses a crisp, executive-ready voice that is direct yet courteous. Prioritizes clarity, brevity, and outcome-focused language in announcements. Strives to keep the group aligned and punctual.",
"Speaks in a friendly, conversational way with contractions and relaxed phrasing. Keeps announcements approachable and down-to-earth, focusing on what people need to know. Wants the group to stay on track while keeping it upbeat.",
"Prefers a warm, informal vibe with simple, chatty sentences and the occasional light exclamation. Keeps things short and easy to scan. Tries to nudge the team to be on time without formality.",
"Uses a laid-back, peer-to-peer tone, skipping formal greetings and sign-offs. Leans on casual wording and straightforward asks. Keeps reminders friendly to encourage punctuality."
] |
To announce a meeting agenda that keeps the group on time, start by clearly stating the meeting\'s objective and expected duration. Then, outline the key topics to be discussed, allocating specific time slots for each. Finally, remind attendees to arrive prepared and to stay on track by adhering to the scheduled agenda.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What’s a good way to summarize a complex bug for engineers and non-engineers together?
|
One summary favors a clear storyline and impact, another balances user impact with technical details and next steps, and another standardizes terminology, reproduction steps, and scope statements.
|
Differences are in level of normalization (steps, definitions, severity), not in overt stylistic signals.
|
Formal
| 5
|
I routinely brief mixed technical and non-technical stakeholders on software defects. I prioritize precise, unambiguous wording, complete sentences, and clearly defined terms. My summaries are structured with context, impact, root cause (if known), mitigations, and next steps.
|
[
"I explain bugs to engineers and non-engineers often. I keep it friendly and easy to follow, with plain language and quick examples. I avoid heavy jargon unless someone asks.",
"When a tricky issue comes up, I keep everyone in the loop in a relaxed, conversational way. I favor short sentences and a quick TL;DR up front. I add a simple analogy if it helps.",
"I share defect updates with cross-functional teams. I deliver concise, polished summaries that emphasize impact, status, and ownership. Jargon is minimized and expectations are clear.",
"I prepare brief issue notes for stakeholders across product and engineering. I focus on clarity, prioritization, and actionable next steps. My updates are succinct and suitable for business reviews.",
"I update mixed audiences about bugs in a straightforward, conversational style. I use everyday language and quick callouts so it is easy to skim. I only dive deeper if people ask."
] |
To summarize a complex bug effectively for both engineers and non-engineers, consider structuring your explanation with context, impact, root cause (if known), mitigations, and next steps. Use precise, unambiguous wording, complete sentences, and clearly defined terms to ensure everyone understands the issue. This approach helps engineers grasp the technical aspects, while non-engineers can follow the logical flow and see the bigger picture.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Give me a framework to evaluate whether to buy or build an internal tool.
|
One will emphasize practical considerations and immediate effort, another aligns to costs, risks, and strategic fit, and another formalizes criteria, weighting, and governance.
|
Variation shows in rigor (scoring matrices, assumptions logs) rather than obvious tone markers.
|
Casual
| 5
|
A team member weighing buy-or-build for internal tools who likes no-nonsense, plain-English guidance. Prefers quick checklists, practical examples, and a friendly tone that gets to the point.
|
[
"A stakeholder evaluating buy-versus-build decisions for internal tools who prefers concise, structured guidance. Expects clear criteria, organized steps, and standard business terminology.",
"An evaluator responsible for internal tooling decisions who requires precise, fully articulated guidance. Seeks unambiguous definitions, comprehensive criteria, and grammatically rigorous explanations.",
"A team member assessing whether to buy or build an internal solution who values polished, business-appropriate communication. Looks for succinct recommendations, risk considerations, and well-structured decision matrices.",
"A decision maker overseeing internal tool selection who expects exacting, formally stated frameworks. Prefers complete sentences, explicit assumptions, and logically rigorous justification.",
"A stakeholder determining buy-versus-build for internal platforms who wants refined, executive-ready guidance. Appreciates crisp phrasing, clear checkpoints, and measurable evaluation metrics."
] |
To evaluate whether to buy or build an internal tool, consider the following framework:
1. **Define the tool's purpose**: Clearly articulate the tool's goals, objectives, and expected outcomes.
2. **Assess the tool's complexity**: Determine the tool's level of complexity, including its functionality, scalability, and integrations.
3. **Evaluate the development resources**: Assess the time, budget, and expertise required to build the tool in-house.
4. **Research existing solutions**: Investigate commercial off-the-shelf (COTS) tools that meet your requirements, considering factors like cost, features, and vendor support.
5. **Weigh the pros and cons**: Compare the benefits of buying a COTS tool (e.g., faster implementation, lower upfront costs) against the benefits of building the tool in-house (e.g., customization, control over development).
6. **Make an informed decision**: Based on your evaluation, decide whether to buy or build the tool, considering factors like your organization's resources, risk tolerance, and strategic priorities.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How should I phrase a reminder to a teammate who hasn’t responded to a data request?
|
One response uses a friendly nudge and a clear ask, another balances urgency with accountability and offers support, and another specifies deadlines, dependencies, and record-keeping.
|
Cues include the explicitness of timelines, dependency framing, and request formalization without overt register words.
|
Formal
| 5
|
A colleague who writes with meticulous grammar, full sentences, and courteous salutations and sign-offs. Avoids contractions and slang. Prefers clearly structured messages that cite dates and deliverables.
|
[
"A colleague who favors polished, business-appropriate messages that are concise and clear. Uses a courteous greeting and a brief, action-focused body with a friendly, polished closing. Comfortable with contractions when they aid readability.",
"A teammate who prefers conversational, friendly messages with a relaxed tone. Often uses contractions and light expressions to keep things approachable. Keeps reminders short and direct without extra formalities.",
"Communicates like chatting in the hallway—straightforward and warm. Uses everyday language and a quick thanks to keep it approachable. Skips elaborate openings and sign-offs.",
"Values clear, succinct emails that get to the point while maintaining a respectful tone. Uses a descriptive subject line, a short context sentence, and a polite call to action. Avoids stiff phrasing and keeps it workplace-appropriate.",
"Writes crisp messages suited for workplace communication, focusing on clarity and timelines. Starts with a polite greeting, outlines the request, and ends with a courteous closing. Keeps language smooth and approachable rather than stiff."
] |
Please note that your response to the data request is urgently needed to proceed with the project. Could you kindly provide an update by the end of the day?
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Propose a structure for a post-mortem meeting after a missed deadline.
|
One structure centers on what happened and fixes, another adds owners, timeline, and stakeholder impact, and another formalizes root cause analysis, action tracking, and verification criteria.
|
Differences come from inclusion of formal RCA methods and validation plans versus pragmatic discussion points.
|
Professional
| 5
|
A team lead who favors polished, business-appropriate language and a composed tone. Values concise, well-structured agendas and objective phrasing. Expects specific next steps and owners.
|
[
"A teammate who likes a conversational tone with everyday language and contractions. Prefers straightforward bullet points and plain talk over corporate phrasing. Comfortable with an approachable, collaborative vibe.",
"An easygoing contributor who appreciates friendly, down-to-earth wording. Likes simple outlines and quick, to-the-point notes. Open to relaxed phrasing if it keeps momentum.",
"A collaborator who favors messages that feel like a chat and sound natural. Enjoys practical tips in simple language and encourages a supportive tone. Not concerned with polished wording as long as it’s clear.",
"A coordinator who expects precise, meticulous wording and fully articulated sentences. Prefers rigorous structure, unambiguous terminology, and a measured, objective tone. Values thoroughness and clarity over brevity.",
"A stakeholder who favors exact phrasing, proper register, and consistent terminology. Prefers a carefully ordered agenda with defined sections and complete, grammatically correct prose. Prioritizes accuracy and adherence to standard business register."
] |
A post-mortem meeting structure should include the following elements: I. Introduction and Context - Briefly introduce the purpose of the meeting, review the project timeline, and set the context for the discussion. II. Root Cause Analysis - Identify the primary reasons for missing the deadline, including any technical, resource, or communication challenges. III. Lessons Learned - Document key takeaways and best practices that can be applied to future projects. IV. Action Items and Recommendations - Outline specific actions to be taken to prevent similar delays in the future, including any necessary adjustments to project planning, resource allocation, or communication protocols. V. Conclusion and Next Steps - Summarize the key findings and action items, and establish a clear plan for implementation and follow-up.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What should a concise project charter include for a two-month initiative?
|
One list covers goals and roles simply, another adds success metrics, risks, and timeline, and another includes scope boundaries, assumptions, and approval criteria.
|
Perceivability arises from the completeness and precision of the charter elements rather than tone.
|
Casual
| 5
|
I run short, two-month projects and want a crisp, no-fluff charter. Keep it straightforward and easy to skim, with just the essentials. Plain language beats buzzwords.
|
[
"I manage two-month initiatives and need a clear, concise project charter. Please keep it structured and actionable, focusing on essentials. Use business-appropriate language and avoid unnecessary jargon.",
"I oversee two-month initiatives and require a precise, rigorously written project charter. Provide a structured outline with complete sentences and unambiguous terminology. Avoid colloquialisms.",
"I lead short initiatives of about two months and am seeking a succinct, well-organized project charter. Emphasize clarity, roles, and deliverables in a businesslike tone. Keep the document practical and results-oriented.",
"I supervise two-month projects and expect a formally composed, meticulously structured project charter. Use definitive phrasing, full sentences, and precise terminology throughout. Brevity is welcome, but completeness and exactness are paramount.",
"I coordinate two-month efforts and prefer a concise, polished charter. Present the essentials in a logical, sectioned format suitable for stakeholders. Maintain a professional register without sounding overly stiff."
] |
A concise project charter should include the project name, objectives, scope, deliverables, timeline, and key stakeholders. It should be straightforward, easy to skim, and focus on the essentials, using plain language over buzzwords.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Help me craft talking points for aligning two teams with overlapping mandates.
|
One set emphasizes shared goals and immediate coordination steps, another frames objectives, responsibilities, and milestones, and another sets formal scope delineations and change control.
|
Differences lie in whether emphasis is on rapport, on outcome alignment, or on formal boundaries and governance.
|
Casual
| 5
|
I’m pulling together talking points to get two teams on the same page. Keep the wording friendly and straightforward, with clear steps and plain English. I like concise bullets I could use in a quick check-in.
|
[
"I am preparing talking points to align two teams with overlapping responsibilities. Use polished, business-appropriate language with a clear structure and actionable outcomes. Keep it concise and collaborative.",
"I prefer a polished tone with crisp, well-organized bullets that emphasize objectives, responsibilities, and next steps. The language should be courteous and confident, avoiding slang. Brevity and clarity are important.",
"Provide talking points in a refined, workplace-appropriate style that supports alignment between two teams. Use clear headings and balanced phrasing, focusing on outcomes and coordination. Maintain a constructive, respectful tone.",
"I require meticulously crafted talking points suitable for a briefing to align two teams. Employ precise terminology, complete sentences, and an orderly progression from objectives to actions. Avoid colloquial expressions.",
"Please present the talking points with rigorous grammar and unambiguous wording. Organize the content systematically, ensuring clarity of scope, responsibilities, and follow-up procedures. Maintain a consistently elevated register."
] |
To align two teams with overlapping mandates, follow these steps:
• Identify the shared goals and objectives of both teams.
• Determine the areas of overlap and potential conflicts.
• Establish clear communication channels and regular meetings.
• Define roles and responsibilities to avoid duplication of effort.
• Develop a plan to integrate resources and expertise.
• Monitor progress and adjust the plan as needed.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How should I introduce a new process for code reviews to the team?
|
One introduction focuses on benefits and simple steps, another includes rationale, roles, and metrics, and another outlines definitions, compliance, and escalation pathways.
|
Cues come from the presence of formal policy elements and evaluation criteria rather than overt style.
|
Casual
| 5
|
I’m rolling out a new code review process with my software team and could use clear, practical steps. Keep it straightforward, with a few examples or lightweight templates I can share.
|
[
"I am preparing to introduce a new code review process to my software team and need a concise, actionable plan. Please provide clear steps, example artifacts, and a suggested rollout timeline.",
"I am looking to implement a new code review process with my software team and would appreciate well-structured, practical guidance. Outline responsibilities, communication points, and a phased rollout. Include links to sample checklists or templates.",
"I need a plan to introduce a new code review process to my software team. Provide a brief proposal structure, key milestones, and success criteria suitable for a typical engineering setting.",
"I intend to implement a new code review process for my software team and require a structured, comprehensive methodology. Supply sequential phases, defined roles and responsibilities, governance considerations, and measurable outcomes.",
"I seek a rigorous plan for introducing a new code review process to my software team. Please deliver a methodical framework with scope, change management steps, approval gates, and post-implementation evaluation. Clarity and completeness are essential."
] |
To introduce a new process for code reviews, start by explaining the reasons behind the change and how it will benefit the team. Be clear about what the new process entails, what changes team members can expect, and how it will improve the overall quality of the code. Provide a clear timeline for the implementation and offer support and resources to help team members adapt to the new process.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Advise me on writing a short update after a pivot in priorities.
|
One approach uses clear, direct explanation and next steps, another maps changes to objectives and stakeholders, and another documents rationale, scope change, and approvals.
|
Perceivability stems from level of documentation and change-control language, not explicit tone.
|
Casual
| 5
|
Writes quick, friendly team updates with contractions and a warm, straightforward vibe. Wants help drafting a short note about a shift in priorities that feels human and easy to skim.
|
[
"Prefers polished, concise language with a confident, neutral tone and no slang. Looking for guidance to write a succinct update about a priority shift for colleagues.",
"Aims for an even, business-appropriate voice that reads well in company channels. Wants a brief, well-structured update on the new priorities that stays crisp and respectful.",
"Focuses on clarity, brevity, and measurable next steps; avoids emojis and casual phrasing. Needs help shaping a short, executive-ready note about changed priorities.",
"Values precise wording, complete sentences, and a ceremonious tone suitable for official notices. Requests advice on drafting a brief announcement regarding a pivot in priorities.",
"Uses meticulous grammar, respectful salutations, and an impersonal voice. Seeks a compact message conveying the revised priorities with exactness and decorum."
] |
Let’s focus on the new priorities for the next quarter. We’ll adjust our current projects to align with the updated goals. If you have any questions or concerns, feel free to reach out to the team.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What’s an effective way to introduce constraints in a brainstorming session without limiting creativity?
|
One approach frames constraints as helpful guardrails, another ties them to goals and resource realities, and another defines scope, criteria, and evaluation stages.
|
Differences appear in how constraints are justified and codified, ranging from conversational framing to formal criteria.
|
Casual
| 5
|
Facilitates brainstorming at work and wants to add guardrails without killing the vibe. Prefers practical, step-by-step tips with quick examples. Likes straightforward, friendly wording that’s easy to follow.
|
[
"Facilitates brainstorming at work and aims to introduce guardrails while preserving creative momentum. Prefers clear, actionable guidance with concise examples. Values polished, business-appropriate wording.",
"Facilitates brainstorming at work and is looking to frame constraints that still encourage inventive thinking. Seeks succinct, practical steps with brief examples. Appreciates a refined, workplace-appropriate tone.",
"Facilitates brainstorming at work and wants to set boundaries that maintain originality. Looks for direct, implementable guidance with short examples. Favors a concise, polished style suitable for business settings.",
"Facilitates brainstorming at work and intends to institute constraints without suppressing divergent thinking. Requires precise, structured recommendations accompanied by brief illustrative examples. Expects grammatically rigorous, carefully structured language.",
"Facilitates brainstorming at work and aims to apply boundary conditions while safeguarding creative exploration. Desires methodical, stepwise recommendations with succinct exemplars. Prefers precise, measured diction and complete sentences."
] |
Introduce constraints through open-ended questions, such as “How might we achieve this goal while considering these limitations?” or “What are the top 3 ideas that could work within this timeframe?”
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Suggest a template for weekly progress notes that people will actually use.
|
One template favors brevity and ease, another balances outcomes, blockers, and next steps, and another includes standardized fields, metrics, and review acknowledgments.
|
Cues involve field specificity, standardization, and documentation practices rather than overt phrasing.
|
Formal
| 5
|
A detail-oriented individual who routinely documents weekly progress. Prefers precise, fully articulated sentences and an orderly structure. Seeks a clear, pragmatic template that promotes clarity and consistency.
|
[
"Tracks weekly updates and likes things to be simple and easy to fill out. Uses friendly, conversational wording and avoids fuss. Wants a template that captures what matters without extra hoops.",
"Prepares weekly updates and values concise, polished language. Favors a clean structure that’s easy to scan. Looking for a practical template that supports consistency and adoption.",
"Jots down progress each week and prefers plain, everyday phrasing. Appreciates a no-frills layout that feels quick to use. A template that keeps things straightforward would hit the spot.",
"Produces weekly summaries and aims for crisp, business-appropriate communication. Prefers a streamlined layout with clear headings. Seeks a pragmatic template that balances brevity and completeness.",
"Sums up the week in a down-to-earth, conversational style. Likes clear prompts and minimal formality so it doesn’t feel like a chore. Wants something easy to stick with week after week."
] |
Here is a suggested template for weekly progress notes that people will actually use:
1. Date: [Insert date]
2. Goals for the week: [List specific, measurable goals]
3. Progress: [Briefly describe progress made towards goals]
4. Challenges: [Identify any challenges faced and how they were addressed]
5. Action items for next week: [List specific tasks to be completed next week]
6. Notes: [Any additional notes or comments]
This template provides a clear and structured format for tracking weekly progress, making it easier to stay on top of tasks and goals.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How can I explain a pricing change to current customers with minimal churn?
|
One explanation leads with value and empathy, another ties changes to costs and roadmap, and another provides formal change notices, timelines, and options.
|
Signals are in the presence of structured options, dates, and policy language versus narrative value framing.
|
Formal
| 5
|
A manager of a subscription service who must inform existing customers about an impending price adjustment. Prefers precise, complete messaging with unambiguous wording and proper terminology to preserve trust and minimize attrition. Seeks structured guidance on the announcement sequence and polished phrasing.
|
[
"A manager of a subscription service who needs to let current customers know prices are going up. Wants friendly, down-to-earth wording with contractions and simple explanations to keep folks from bailing. Looking for easy steps and sample lines.",
"Runs a subscription service and has to break the news about a price bump to existing customers. Likes a warm, conversational vibe that feels honest and human, without stuffy wording. Wants quick pointers and a few example messages.",
"Handles a subscription product and needs to explain a price change to customers who are already onboard. Prefers a straightforward, friendly tone that sounds like a real person and keeps things chill. Hopes for simple guidance and a couple of ready-to-use blurbs.",
"Oversees a subscription service and needs to communicate a price increase to current customers. Values clear, business-appropriate language that is confident and respectful, avoiding jargon. Seeks a stepwise plan and concise message examples to limit churn.",
"Leads a subscription offering and must announce a pricing update to existing customers. Prefers polished, client-facing communication that is direct, empathetic, and on-brand. Wants a practical rollout plan and succinct templates."
] |
To minimize customer churn, it is essential to communicate the pricing change clearly and transparently. Consider sending a notification 30-60 days prior to the change, explaining the reasons behind the adjustment and highlighting any added value customers will receive. Use straightforward language, avoiding jargon or technical terms that might confuse customers. Emphasize the benefits of the change, such as improved service quality or additional features, and provide a clear timeline for the adjustment. If possible, offer a grandfathered rate for existing customers who are unable or unwilling to pay the new price. This approach demonstrates empathy and a commitment to customer satisfaction, helping to maintain trust and loyalty.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
I need to reconcile conflicting feedback on a draft proposal. How should I proceed?
|
One approach encourages a clarifying conversation and synthesis, another proposes criteria, prioritization, and stakeholder mapping, and another formalizes decision rules and documentation of trade-offs.
|
Differences emerge through explicit decision frameworks and traceability rather than overt tone.
|
Casual
| 5
|
Collaborates on shared drafts where multiple people chime in with clashing comments. They’re into clear, no‑nonsense tips they can try right away. Keep it friendly and straight to the point so they can sort things out fast.
|
[
"Routinely manages input from several stakeholders on proposal drafts. Values concise, structured recommendations that can be implemented efficiently. Prefers a polished, business-appropriate tone.",
"Frequently coordinates revision cycles with multiple reviewers. Expects thorough, logically ordered guidance with precise terminology. Values completeness and rigor in explanations.",
"Manages proposal iterations that bring in feedback from peers and leads. Looks for succinct, actionable steps with brief rationale to align reviewers. Communication should be clear, polished, and easy to share.",
"Oversees formal review processes where comments may conflict. Requires detailed, stepwise instructions supported by explicit criteria and unambiguous language. Maintains exact grammar and professional diction.",
"Regularly consolidates stakeholder comments on working drafts. Seeks practical, well-structured advice that is easy to communicate to a team. Prefers refined, professional wording throughout."
] |
To reconcile conflicting feedback on a draft proposal, first, identify the key areas of disagreement. Then, categorize the feedback into constructive and non-constructive comments. Address the constructive comments by incorporating the suggested changes and providing a clear explanation for any deviations. For non-constructive comments, focus on maintaining a professional tone and avoid taking it personally. Finally, compile the revised proposal and share it with the stakeholders, ensuring that all feedback has been addressed.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Outline steps to prepare a non-technical demo of a technical feature.
|
One plan emphasizes relatable scenarios and simplicity, another aligns value to buyer needs and outcomes, and another ensures precise terminology boundaries and avoids overclaims.
|
Perceivability is in the handling of definitions, disclaimers, and structure of benefits versus stories.
|
Formal
| 5
|
Preparing a non-technical demo of a technical feature. Expects precise, fully articulated sentences, no contractions, and professional terminology where appropriate. Prefers structured outlines with numbered steps and unambiguous phrasing.
|
[
"Preparing a non-technical demo of a technical feature. Expects polished, business-appropriate language that is concise and clear. Prefers clean bullet points, action-focused headings, and straightforward explanations.",
"Preparing a non-technical demo of a technical feature. Values a confident, workplace-ready tone with crisp sentences and tidy structure. Seeks clarity and brevity without sounding stiff.",
"Preparing a non-technical demo of a technical feature. Likes friendly, conversational wording with contractions and everyday examples. Prefers easygoing phrasing that cuts the jargon.",
"Preparing a non-technical demo of a technical feature. Wants relaxed explanations that feel like a chat, with relatable metaphors and plain language. Fine with a light, personable vibe.",
"Preparing a non-technical demo of a technical feature. Favors short, breezy sentences, informal transitions, and a warm tone. Comfortable with casual phrasing over formal definitions."
] |
To prepare a non-technical demo of a technical feature, follow these steps: 1. Identify the key benefits and value proposition of the feature. 2. Determine the target audience and their level of technical understanding. 3. Develop a clear and concise narrative that explains the feature in simple terms. 4. Use visual aids such as diagrams, flowcharts, or videos to illustrate complex concepts. 5. Practice the demo to ensure a smooth and engaging presentation. 6. Be prepared to answer questions and provide additional information as needed.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What should I include in a short competitive brief for internal use?
|
One brief focuses on highlights and quick takeaways, another ties strengths/weaknesses to our positioning, and another establishes criteria, sources, and formal scoring.
|
Variation appears in rigor of evidence, source notes, and evaluation rubric versus headline comparisons.
|
Casual
| 5
|
I’m putting together a short internal competitive brief and just want a quick, skimmable checklist. Keep it super practical with the essentials we actually use to make decisions. No fluff—plain English is perfect.
|
[
"I am preparing a short internal competitive brief and need a concise, well-structured checklist. Please use clear, business-appropriate language focused on decision-relevant insights. Efficiency and clarity are priorities.",
"I’m drafting a short internal competitive brief and prefer a polished, organized outline. Keep the guidance succinct, with actionable points suitable for cross-functional stakeholders. Clarity and practicality are key.",
"I’m assembling a brief internal competitive summary and would value a crisp checklist with clear headings. Use professional terminology and keep each item actionable and concise. The tone should be polished and to the point.",
"I am preparing a concise internal competitive brief and require a rigorously structured checklist. Employ precise terminology, complete sentences, and unambiguous phrasing. Emphasize decision-critical elements in a comprehensive yet succinct manner.",
"I am compiling a short internal competitive brief and seek a methodical, exhaustive checklist. Maintain formal diction and grammatical precision throughout. Prioritize clarity, completeness, and objective phrasing."
] |
A short competitive brief should include the following essentials:
1. Project goals and objectives
2. Target audience and their needs
3. Key competitors and their strengths/weaknesses
4. Unique selling points and differentiators
5. Budget and timeline
6. Key performance indicators (KPIs) for success
7. Any specific requirements or constraints
This will provide a clear and concise overview of the project, helping to ensure everyone is on the same page and working towards the same goals.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How do I acknowledge a mistake in a team channel without derailing morale?
|
One response emphasizes ownership and reassurance, another adds mitigation steps and next actions, and another documents cause, corrective actions, and follow-up verification.
|
Cues lie in the specificity of corrective plans and verification, not the surface tone.
|
Formal
| 5
|
A team contributor who communicates with precise, grammatically rigorous language and complete sentences. Prefers careful structure, measured wording, and precise terminology when addressing issues. Values accountability expressed in a composed, respectful manner.
|
[
"A teammate who speaks in a relaxed, conversational way with contractions and friendly phrasing. Leans on simple words, warmth, and a supportive vibe when admitting slip-ups. Tries to keep things light without sounding dismissive.",
"A colleague who prefers informal chat-style messages and keeps it personable. Uses everyday language and a touch of encouragement to keep the team upbeat. Keeps explanations straightforward and down-to-earth.",
"A team member who writes like they talk—brief, friendly, and approachable. Comfortable acknowledging goofs with plain wording and a bit of lightness. Avoids stiff phrasing to keep momentum.",
"A colleague who favors polished, business-appropriate wording without sounding stiff. Communicates succinctly, with respectful tone and clear ownership. Aims to reassure the team while keeping messages focused and constructive.",
"A teammate who writes in a refined, workplace-ready style that balances clarity and warmth. Chooses concise, polite phrasing and avoids slang. Emphasizes accountability while keeping the conversation productive."
] |
I appreciate your feedback. To acknowledge a mistake in a team channel without derailing morale, I suggest being transparent about the issue, taking ownership of the mistake, and focusing on the solution. This can be done by saying something like, 'I realize I made an error, and I'm working on a fix. I'll keep you updated on the progress.' This approach shows accountability, respect for the team's time, and a commitment to finding a solution, which can help maintain morale and productivity.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Propose a way to introduce an internal glossary for common terminology.
|
One method shares simple definitions and examples, another aligns to onboarding and usage policies, and another sets ownership, versioning, and approval workflow.
|
Differences show in governance and versioning details versus approachable examples.
|
Formal
| 5
|
A staff member responsible for internal documentation quality and consistency. Prefers precise, fully articulated explanations with correct grammar and terminology. Seeks a structured, step-by-step plan for rolling out a glossary across teams.
|
[
"A team lead coordinating documentation updates across departments. Expects polished, business-appropriate guidance that’s clear and concise. Wants an actionable plan to launch a shared glossary without disrupting workflows.",
"An operations analyst helping standardize internal language. Values crisp, executive-ready communication and clear ownership. Looking for a practical, stakeholder-friendly approach to introducing a common terminology glossary.",
"A teammate who helps keep docs tidy. Likes conversational explanations with straightforward next steps. Looking for an easy way to roll out a shared glossary without a lot of red tape.",
"A contributor who wants everyone using the same terms. Prefers friendly, plain-language guidance with quick bullets and examples. Hopes for a simple rollout that folks can adopt fast.",
"A colleague supporting internal onboarding materials. Appreciates down-to-earth, conversational guidance and clear, no-fuss actions. Wants a painless way to get a common glossary in front of the team."
] |
To introduce an internal glossary for common terminology, consider the following steps: 1. Identify key stakeholders and teams that will be impacted by the glossary. 2. Define the scope and purpose of the glossary, including the types of terms it will cover and the audience it will serve. 3. Develop a governance model to ensure the glossary is maintained and updated regularly. 4. Create a process for submitting and reviewing new terms, including a clear decision-making process for inclusion or exclusion. 5. Establish a format and structure for the glossary, including any necessary metadata or categorization. 6. Communicate the glossary to all relevant teams and stakeholders, and provide training or support as needed. 7. Monitor and evaluate the effectiveness of the glossary, and make adjustments as necessary.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How can I debrief a client meeting that went off-track and regain momentum?
|
One approach recaps key points and aligns on next steps, another documents outcomes and action owners, and another issues a formal summary with scope, decisions, and pending items.
|
Signals include the degree of formality in documenting decisions and responsibilities, not explicit tone words.
|
Formal
| 5
|
A client-facing practitioner seeking a structured approach to debrief a meeting that deviated from its objectives. Prefers precise, comprehensive guidance with clear steps for stakeholder follow-up, documentation, and restoring alignment. Values unambiguous wording and professional etiquette.
|
[
"A client-facing practitioner looking for a practical plan to debrief a meeting that ran off course. Prefers polished, business-ready guidance with clear next steps for follow-up and re-alignment. Values concise recommendations and a confident tone.",
"A client-facing practitioner who wants a well-organized plan to recap a meeting that missed the mark. Appreciates clear, actionable next steps and business-appropriate language. Seeks a confident, results-focused tone.",
"I work with clients and need help regrouping after a meeting that went sideways. I like straightforward tips with plain language and quick, doable steps. Keep it friendly and to the point.",
"I’m client-facing and trying to bounce back from a meeting that got derailed. Give me simple, no-nonsense advice I can act on right away. A conversational tone helps.",
"I handle client meetings and want to fix the vibe after one went off-track. Short, practical pointers and a friendly, approachable style are ideal. I’m looking for steps I can use today."
] |
To regain momentum after a client meeting that went off-track, follow these steps: 1. Acknowledge the deviation: Recognize the meeting's departure from its objectives and express understanding for the client's concerns. 2. Re-establish the agenda: Politely interrupt the discussion and reiterate the meeting's agenda, focusing on the key topics. 3. Refocus the discussion: Guide the conversation back on track by asking open-ended questions related to the agenda items. 4. Document the discussion: Take notes on the client's concerns and the agreed-upon next steps. 5. Summarize and confirm: Recap the meeting's outcomes, ensuring both parties are aligned on the actions and responsibilities. 6. Schedule a follow-up: Plan a subsequent meeting to review progress and address any remaining concerns. By following these steps, you can effectively debrief a client meeting, regain momentum, and maintain a productive working relationship.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What’s a good pattern for writing clear acceptance criteria for a user story?
|
One pattern uses concrete examples and outcomes, another uses standardized formats and edge cases, and another formalizes conditions, preconditions, and testable statements.
|
Perceivability comes from the precision and completeness of conditions and structure rather than tone.
|
Formal
| 5
|
A product team member drafting user stories who wants guidance that is precise and unambiguous. Prefers complete sentences, exact terminology, and rigorous grammar when discussing process. Expects structured explanations suitable for official documentation.
|
[
"A product team member drafting user stories who wants guidance that is polished and business-appropriate. Prefers concise, stakeholder-ready explanations that are clear without sounding stiff. Comfortable with a professional tone across examples.",
"A product team member drafting user stories who wants guidance in a relaxed, conversational voice. Prefers friendly wording, contractions, and plain talk when explaining how to write acceptance criteria. Likes examples that feel informal and approachable.",
"A product team member drafting user stories who wants advice that reads cleanly in internal reports. Prefers a crisp, professional register that is clear and direct without jargon overload. Values succinct, businesslike phrasing.",
"A product team member drafting user stories who wants tips explained like a teammate would talk. Prefers everyday language with contractions and light, friendly phrasing in the examples. Comfortable with a laid-back tone.",
"A product team member drafting user stories who wants guidance that feels personable and conversational. Prefers simple, down-to-earth language with an easygoing cadence. Enjoys approachable, friendly examples."
] |
A good pattern for writing clear acceptance criteria for a user story is to use the Arrange, Act, Assert (AAA) pattern. This involves clearly defining the preconditions, the action taken, and the expected outcome. For example:
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Advise me on responding to a critical comment on a public thread about our product.
|
One response stresses empathy and direct resolution, another adds accountability and escalation paths, and another uses formal acknowledgment, references to policy, and documented remediation steps.
|
Differences are in the documentation and policy anchoring versus conversational reassurance.
|
Professional
| 5
|
Writes polished, business-appropriate replies for public-facing conversations. Balances empathy with accountability and keeps sentences clear and concise. Avoids slang while staying approachable. Prefers structured guidance with actionable steps.
|
[
"Speaks in a friendly, conversational way with contractions and simple phrasing. Keeps things approachable and avoids corporate buzzwords. Comfortable sounding personable in public threads.",
"Likes a down-to-earth voice that feels like chatting with a customer. Uses everyday language and a relaxed tone, sometimes lightening tension with warm phrasing. Keeps recommendations straightforward and easy to follow.",
"Leans into a human, informal vibe that shows openness and warmth. Chooses short, conversational sentences and avoids stiff phrasing. Focuses on sounding relatable in public replies.",
"Prefers precise, carefully composed sentences with full grammar and measured phrasing. Avoids colloquialisms and maintains a courteous distance in public statements. May reference documented facts and policy when applicable.",
"Uses refined, meticulous language with complete sentences and respectful salutations. Keeps tone restrained and authoritative, steering clear of contractions or casual expressions. Emphasizes clarity and correctness."
] |
I appreciate you bringing this to our attention. Can you please provide more details about the issue you're experiencing with our product? This will help us to better understand the problem and provide a more effective solution.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Suggest a structure for an internal memo proposing a tooling change.
|
One structure highlights pain points and a practical solution, another evaluates options with costs and benefits, and another includes formal criteria, risks, and implementation governance.
|
Cues are the presence of risk registers, evaluation rubrics, and sign-off requirements rather than overt stylistic markers.
|
Casual
| 5
|
Prepares internal memos proposing tooling changes to coworkers. Uses a friendly, conversational voice with simple headings and plain English. Prioritizes clarity, brevity, and actionable next steps.
|
[
"Prepares internal memos proposing tooling changes to coworkers. Uses a polished, business-appropriate tone with concise headings and standard sections. Prioritizes clarity, brevity, and actionable next steps.",
"Prepares internal memos proposing tooling changes to coworkers. Uses precise, grammatically rigorous language with fully articulated sections and defined terms. Prioritizes clarity, brevity, and actionable next steps.",
"Prepares internal memos proposing tooling changes to coworkers. Uses a crisp, businesslike voice with neutral wording, limited contractions, and clean structure. Prioritizes clarity, brevity, and actionable next steps.",
"Prepares internal memos proposing tooling changes to coworkers. Uses precise terminology, complete sentences, and carefully structured sections with explicit justifications. Prioritizes clarity, brevity, and actionable next steps.",
"Prepares internal memos proposing tooling changes to coworkers. Uses a clear, executive-ready tone guided by standard business writing conventions and concise summaries. Prioritizes clarity, brevity, and actionable next steps."
] |
Here is a suggested structure for an internal memo proposing a tooling change:
I. Introduction
- Briefly explain the purpose of the memo and the proposed tooling change.
II. Problem Statement
- Describe the current challenges or issues with the existing tooling.
III. Proposed Solution
- Clearly outline the proposed tooling change, including any new features or improvements.
IV. Benefits
- Explain the benefits of the proposed tooling change, including any cost savings, increased efficiency, or improved user experience.
V. Next Steps
- Outline the next steps for implementing the proposed tooling change, including any necessary approvals or timelines.
VI. Conclusion
- Summarize the key points and reiterate the importance of the proposed tooling change.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How should I prepare talking points for a brief update to the board?
|
One set emphasizes headline progress and clarity, another ties metrics to strategy and runway, and another uses precise definitions, methodology, and variance contexts.
|
Perceivability lies in the granularity of metric definitions and methodological qualifiers rather than tone.
|
Professional
| 5
|
Preparing a brief update for the board and wants succinct, polished talking points. Prefers clear, business-ready language with a confident tone, avoiding slang yet not overly formal. Comfortable with concise bullets focused on outcomes and next steps.
|
[
"Preparing a quick board update and wants friendly, conversational talking points. Likes plain language, contractions, and light phrasing that feels natural rather than corporate.",
"Getting ready for a short board check-in and prefers tips that sound like everyday conversation. Appreciates simple wording, a relaxed tone, and punchy bullets without jargon.",
"Needs help shaping a brief board update using easygoing, approachable language. Wants straightforward points with a human, upbeat voice and minimal formality.",
"Preparing a concise board update and prefers meticulously structured guidance. Expects complete sentences, precise wording, and professional terminology with no colloquialisms.",
"Drafting a brief report for the board and seeks rigorously composed talking points. Values formal diction, unambiguous phrasing, and fully articulated recommendations."
] |
To prepare talking points for a brief update to the board, focus on key outcomes and next steps. Use clear, business-ready language and a confident tone. Consider the following points: \* Clearly define the purpose and scope of the update \* Identify key achievements and milestones \* Outline challenges and areas for improvement \* Provide a concise summary of next steps and action items \* Use concise bullets and avoid unnecessary details. This will help you deliver a clear and effective update to the board.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Propose a plan to roll out a small policy change with minimal friction.
|
One plan uses concise messaging and simple steps, another includes stakeholder mapping and feedback loops, and another formalizes notice periods, documentation, and compliance checks.
|
Signals include the presence of formal compliance steps and documentation, not explicit formality cues.
|
Formal
| 5
|
Seeks a concise, structured rollout plan that minimizes operational disruption. Prefers precise wording, complete sentences, and unambiguous steps with timelines, stakeholder notifications, and defined accountability. Values documented risk mitigation and measurable success criteria.
|
[
"Looking for a clear, structured plan to roll out a small policy change with minimal disruption. Values brevity, defined owners and timelines, and straightforward feedback channels. Expects a crisp summary of risks and next steps.",
"Seeks a practical rollout plan that limits friction and keeps teams aligned. Wants clear responsibilities, milestones, and simple ways for people to raise questions. Appreciates a brief summary and a clean status cadence.",
"Needs a business-ready plan for a small policy update that won’t slow delivery. Requests named owners, dates, and a light feedback loop to capture issues. Prefers a succinct overview of risks and contingencies.",
"I need a simple game plan to roll out a small policy tweak without drama. Tell me who’s doing what and when, and give folks an easy way to speak up. Keep it short and easy to follow.",
"Give me a no-fuss rollout plan for a small policy change. A few clear steps, clear owners, quick updates, and an easy feedback path are perfect. Make it straightforward so nobody gets bogged down."
] |
To minimize operational disruption, we will roll out the policy change in three phases over a period of six weeks. Phase one will involve educating stakeholders and employees about the change, starting two weeks prior to implementation. Phase two will be the actual implementation, which will occur on a Friday to minimize impact on business operations. Phase three will involve monitoring and evaluation, with a review of the process after four weeks. Stakeholders will be notified in advance of each phase, and accountability will be clearly defined for each step. Risk mitigation strategies will be documented and implemented to ensure a smooth transition. Success criteria will be measurable and clearly defined, with regular check-ins to assess progress.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What’s the best way to capture meeting notes so decisions don’t get lost?
|
One method emphasizes actionable bullets and clarity, another adds owners, deadlines, and references, and another standardizes decision logs, identifiers, and approval acknowledgments.
|
Differences appear in the level of standardization and traceability elements.
|
Professional
| 5
|
Communicates in a clear, businesslike manner. Prefers concise summaries and structured wording. Appreciates polished language suitable for workplace settings.
|
[
"Communicates in a relaxed, conversational style with contractions and friendly phrasing. Likes quick, plain-language summaries and straightforward next steps.",
"Keeps the tone laid-back and chatty. Prefers short, informal notes and quick back-and-forth messages over polished write-ups.",
"Sounds like a hallway conversation—easygoing and to the point. Comfortable with simple, everyday language and doesn’t fuss over perfect phrasing.",
"Uses precise, fully formed sentences and meticulous grammar. Prefers comprehensive, carefully worded messages with exact terminology.",
"Communicates with high formality and careful word choice. Expects rigorous phrasing, complete sentences, and a consistently professional register."
] |
Use a digital note-taking tool like Evernote, OneNote, or Google Keep to capture meeting notes. These tools allow real-time collaboration, tagging, and searching, ensuring decisions don
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How do I outline a training session for a new internal tool?
|
One outline focuses on quick wins and practice, another includes objectives, modules, and metrics, and another sets prerequisites, detailed outcomes, and assessments.
|
Perceivability is in the explicit learning outcomes and assessment rigor versus approachable sequencing.
|
Casual
| 5
|
I'm planning a training session for a new internal tool and want a straightforward plan. Keep the language relaxed and easy to follow, with clear steps, timing, and what to cover. Make it feel like guidance from a helpful teammate.
|
[
"I'm planning a training session for a new internal tool and need a concise, business-ready outline. Please provide a structured plan with objectives, agenda blocks, timing, and required materials in a polished tone.",
"I’m seeking a workplace-appropriate outline for this training. Present a clear framework with goals, schedule, and key topics, written crisply and suitable for sharing internally.",
"I need a well-organized training outline I can circulate at work. Deliver a succinct plan with objectives, time allocations, and resources, using a professional voice.",
"I require a formally structured outline for a training session on a new internal tool. Use precise terminology, complete sentences, and clearly delineated sections specifying objectives, time allotments, and materials.",
"Please provide a comprehensive training outline presented in a formal register. Employ unambiguous language, fully articulated sentences, and explicitly labeled components such as objectives, schedule, and resources."
] |
To outline a training session for a new internal tool, follow these steps:
1. Define the training objectives and target audience.
2. Determine the scope of the training session, including the topics to be covered and the duration of the session.
3. Create an agenda or outline for the training session, including the introduction, presentation, hands-on exercises, and Q&A session.
4. Prepare any necessary materials, such as presentation slides, handouts, and equipment.
5. Schedule a rehearsal or dry run to ensure everything goes smoothly.
6. Deliver the training session, providing clear instructions and answering questions as needed.
7. Evaluate the effectiveness of the training session and gather feedback from participants.
8. Make any necessary adjustments to the training session based on feedback and evaluation results.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Advise on blending technical and business content in a 10-minute pitch.
|
One approach leans on clear benefits and a simple demo, another maps features to KPIs and stakeholders, and another specifies definitions, assumptions, and risk disclosures.
|
Cues come from whether the content privileges precision and disclosures over narrative brevity.
|
Casual
| 5
|
A product lead preparing a 10-minute pitch for a mixed audience of executives and engineers. Speaks in a friendly, conversational way with contractions and plain, relatable wording. Wants practical guidance on blending technical detail with business value.
|
[
"A product lead preparing a 10-minute pitch for a mixed audience of executives and engineers. Prefers polished, concise language with clear structure and business-appropriate wording; avoids slang. Wants practical guidance on blending technical detail with business value.",
"A product lead preparing a 10-minute pitch for a mixed audience of executives and engineers. Likes a crisp, well-organized tone that sounds confident and business-ready, without colloquialisms. Wants practical guidance on blending technical detail with business value.",
"A product lead preparing a 10-minute pitch for a mixed audience of executives and engineers. Favors a refined, succinct style with tight structure and professional terminology where useful. Wants practical guidance on blending technical detail with business value.",
"A product lead preparing a 10-minute pitch for a mixed audience of executives and engineers. Expects precise, rigorous language with complete sentences and carefully defined terms; no contractions. Wants practical guidance on blending technical detail with business value.",
"A product lead preparing a 10-minute pitch for a mixed audience of executives and engineers. Prefers an exacting, ceremonious tone with fully spelled-out phrasing and meticulous grammar. Wants practical guidance on blending technical detail with business value."
] |
To create a compelling 10-minute pitch, start by identifying your key message and tailoring it to your audience. Allocate 2-3 minutes for technical details, focusing on the most relevant and impactful aspects. Use simple language and avoid jargon to ensure engineers and executives can understand. For the remaining 7-8 minutes, emphasize the business value, highlighting how your solution addresses pain points, increases revenue, or improves efficiency. Use real-world examples and data to support your claims. Practice your delivery to ensure a smooth, engaging presentation that leaves a lasting impression.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How can I make an internal FAQ that reduces repeated questions from the team?
|
One FAQ uses concise Q&A and practical examples, another adds categories, owners, and update cadence, and another sets formal taxonomy, version control, and source of truth policies.
|
Differences lie in governance details and taxonomy rigor rather than overt tone.
|
Formal
| 5
|
A detail-oriented employee who values precise, grammatically correct communication and complete sentences. Prefers structured guidance, defined terminology, and clear standards when documenting an internal FAQ. Expects recommendations to be methodical and unambiguous.
|
[
"A team member looking for polished, actionable steps to establish an internal FAQ that cuts down repeated questions. Values concise, well-organized guidance with clear headings and measurable outcomes. Prefers examples and best practices that can be rolled out across the team.",
"Seeks a practical framework for building a maintainable FAQ that fits everyday workflows. Appreciates crisp language, clear ownership, and a predictable review cadence. Wants guidance that’s ready to implement without unnecessary complexity.",
"Wants easy tips to whip up an internal FAQ so people stop asking the same stuff. Likes quick pointers, plain talk, and examples they can copy. Doesn’t mind starting scrappy and improving later.",
"Looking for a straightforward way to set up a team FAQ fast. Prefers friendly explanations, short lists, and simple templates. Open to trying things and tweaking as they go.",
"Hopes to reduce repeat pings with a simple FAQ that folks actually read. Likes conversational guidance, practical shortcuts, and clear do-this-now steps. Fine with good-enough drafts over perfect wording."
] |
Create a centralized knowledge base where team members can search for answers to frequently asked questions. This can be achieved by documenting common issues, solutions, and best practices in a shared repository. Regularly update the knowledge base to ensure it remains relevant and accurate.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What’s a clear way to document a temporary workaround without confusing people later?
|
One way labels the workaround and next steps plainly, another adds owner, review date, and risks, and another specifies validity, scope, rollback criteria, and record linkage.
|
Signals include explicit scope and deprecation plans versus straightforward guidance.
|
Professional
| 5
|
Documents concise guidance for colleagues. Prefers clear, polished communication suited to workplace readers and easy to reference later. Values consistency and a straightforward, readable structure.
|
[
"Writes quick tips for colleagues. Likes friendly, everyday wording with contractions so people can skim and get it fast. Keeps the tone relaxed and approachable.",
"Shares short how-tos with colleagues. Favors a conversational voice, simple phrases, and examples over stiff wording. Wants it to read like a helpful chat, not policy.",
"Jots down notes for colleagues to follow. Uses plain talk, contractions, and clear callouts. Steers clear of formal phrasing or jargon.",
"Prepares instructional notes for colleagues. Favors precise, grammatically rigorous prose with complete sentences and unambiguous terminology. Avoids colloquialisms.",
"Produces internal guidance for colleagues. Uses strictly formal diction, consistent terminology, and fully articulated sentences to prevent ambiguity. Maintains a composed, impersonal tone."
] |
To document a temporary workaround, use a clear and concise title, such as "Temporary Fix: [Issue]". In the description, explain the problem, the workaround, and any limitations or known issues. Use a standard format, like a Markdown table, to present the information in a readable way. For example:
| Issue | Workaround | Limitations |
| --- | --- | --- |
| [Issue] | [Workaround] | [Limitations] |
This approach helps avoid confusion by clearly labeling the workaround as temporary and providing essential details for users to understand the solution.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Suggest a pattern for writing concise commit messages that aid future audits.
|
One pattern centers on what changed and why in everyday terms, another adds issue links and impact, and another requires structured prefixes, references, and compliance notes.
|
Perceivability arises from structured fields and references rather than overt register differences.
|
Professional
| 5
|
A software developer focused on a maintainable version control history. Prefers clear, actionable guidance and concise, well-structured recommendations. Looking for a practical pattern that supports future audits.
|
[
"I’m a developer who wants a simple, no-nonsense way to write commits. Keep it short, clear, and easy to reuse. It should make audits later way less painful.",
"I write code all day and just need a go-to commit format. Nothing fancy—just something quick that still helps when we audit down the road.",
"Give me a straightforward commit recipe I can follow every time. I don’t want fluff; just the bits that make tracking changes and audits dead simple.",
"I am a software developer seeking a prescriptive template for commit messages. The structure should emphasize scope, intent, and verification to facilitate future audits. Please provide a concise, repeatable method.",
"As a developer, I require a rigorous, unambiguous pattern for commits that supports traceability and compliance reviews. Deliver a precise framework with clearly delineated components."
] |
Use the imperative mood and be concise, e.g., "Fix bug in login feature"
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How should I handle a situation where two teams have conflicting deadlines for shared resources?
|
One approach proposes a quick sync and compromise, another introduces prioritization criteria and escalation paths, and another formalizes arbitration rules, SLAs, and documentation.
|
Differences lie in the explicitness of policies and criteria versus conversational coordination.
|
Professional
| 5
|
Frequently coordinates work where two teams need the same shared resources at overlapping times. Prefers guidance that is polished, concise, and suitable for business communication with tactful phrasing. Looks for clear, actionable steps and sample wording for stakeholder updates.
|
[
"Often runs into overlaps when two teams need the same resources. Likes advice that's friendly, straight to the point, and easy to chat through, with simple examples to copy. Contractions and a relaxed tone work best.",
"Deals with team scheduling clashes on a regular basis. Prefers down-to-earth guidance that reads like a conversation and gets to the point fast. Short, skimmable tips and plain language help.",
"Frequently juggles competing asks for shared tools and people. Wants advice in a friendly, upbeat tone that feels approachable and practical. Comfortable with contractions and quick, informal phrasing.",
"Routinely encounters conflicting timelines for shared resources. Seeks guidance that is precise, fully articulated, and organized with clear structure and terminology. Avoids colloquialisms and expects complete sentences.",
"Manages overlapping resource needs between teams. Prefers instruction with rigorous grammar, unambiguous terms, and no contractions. Values carefully structured, stepwise recommendations."
] |
To handle conflicting deadlines for shared resources, I recommend the following steps: 1. Identify the critical resources and their availability. 2. Prioritize the projects based on their deadlines and resource requirements. 3. Negotiate with the teams to adjust their deadlines or allocate additional resources. 4. Implement a project management tool to track progress and resource utilization. 5. Regularly review and update the resource allocation plan to ensure it remains effective. You can communicate the plan to stakeholders by saying,
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Propose a structure for a short design rationale that others can review quickly.
|
One structure highlights the problem and the chosen approach plainly, another ties trade-offs to goals and constraints, and another specifies alternatives, evaluation criteria, and decision record IDs.
|
Cues include the presence of evaluation criteria and traceable identifiers rather than tone.
|
Casual
| 5
|
I keep design notes short and easy to skim—friendly headers, quick bullets, and plain-talk explanations so folks get the gist fast. I don’t fuss over fancy wording; clarity wins. The goal is speed: reviewers can scan it in a minute and leave comments right away.
|
[
"I communicate in a polished, business-ready tone. I use concise sections, clear bullets, and an explicit problem statement so reviewers can move quickly. The language is direct and free of unnecessary flourish.",
"My write-ups are executive-ready without being verbose. I structure content with brief headings, measurable outcomes, and next steps to keep review cycles efficient.",
"I maintain a crisp, stakeholder-focused voice. I emphasize clarity, concise rationale, and decisions captured in a tidy format, suitable for busy reviewers.",
"I prefer precise, fully articulated sentences and unambiguous terminology. Sections are explicitly labeled and ordered logically, with complete transitions and definitions where needed. Colloquialisms are avoided.",
"My documentation adheres to a rigorous register appropriate for high-stakes review. I present a defined structure with complete sentences, consistent terminology, and explicit criteria to minimize ambiguity."
] |
The response should include a clear and concise explanation of the proposed structure for a short design rationale, including the key elements and their relationships.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What belongs in a brief to prepare a spokesperson for media questions on a new feature?
|
One brief focuses on key points and simple guardrails, another includes audience concerns and bridging statements, and another details approved language, definitions, and contingency responses.
|
Perceivability comes from the precision and control of language and contingencies rather than overt style.
|
Casual
| 5
|
I'm looking for a brief written in plain, everyday language. Keep it friendly, with short sentences, simple phrasing, and easy-to-skim bullets. Avoid buzzwords and keep it straightforward.
|
[
"I prefer a concise, polished brief. Use clear headings, crisp bullets, and business-appropriate wording. Avoid slang and keep the tone confident yet approachable.",
"I'm looking for guidance that reads clean and office-ready. Use structured sections, action-oriented bullets, and a neutral, credible tone. No fluff.",
"Please provide a neat, client-ready outline. Emphasize clarity and brevity. Maintain a respectful, businesslike voice without casual phrasing.",
"I require a precise document written in complete sentences. Use formal terminology where appropriate and maintain rigorous grammar throughout. No contractions or colloquialisms.",
"Prepare a thoroughly composed brief with carefully structured paragraphs. Employ unambiguous language and consistent, formal diction. The tone should remain impersonal."
] |
Here are the key points to include in a brief to prepare a spokesperson for media questions on a new feature:
* Clearly explain the new feature and its benefits
* Provide examples of how the feature will be used in real-world scenarios
* Anticipate common questions and prepare responses
* Emphasize the key selling points and differentiators
* Practice answering questions with the spokesperson to ensure they feel confident and prepared
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How can I ask for input on a draft without creating a long back-and-forth thread?
|
One method suggests targeted, simple questions, another sets review scope and deadlines, and another defines roles, criteria, and acceptance conditions.
|
Differences are in role clarity and formal acceptance criteria versus casual solicitation.
|
Professional
| 5
|
I write succinct, businesslike messages and aim for clear asks. I prefer structured feedback and set expectations upfront to minimize back-and-forth. I avoid slang but keep the tone approachable.
|
[
"I keep messages friendly and chatty, using contractions and simple phrasing. I prefer quick, easy replies and like to keep things relaxed. I’ll skip jargon and keep it light so feedback comes in fast.",
"I’d send a short, conversational note with a TL;DR and a few quick questions. Emojis or a casual sign-off feel natural to me. I want fast input without a bunch of formalities.",
"I talk like I would in a hallway chat—straight to the point but informal. I keep requests brief and friendly so it’s easy to respond. Slang and contractions are fine by me.",
"I favor precise, fully composed requests with complete sentences and clear criteria. I use unambiguous, polished language and proper formatting. I seek comprehensive, consolidated feedback in a single response.",
"I maintain a meticulous, formal tone with salutations and courteous closings. I specify scope, deadlines, and decision criteria explicitly to prevent iterative exchanges. I expect considered, well-structured responses."
] |
Can you please provide feedback on this draft in a concise manner to avoid a lengthy conversation?
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Suggest steps to prepare a concise risk register for a short project.
|
One set lists straightforward risks and mitigations, another categorizes by impact and owner with timelines, and another includes likelihood scoring, triggers, and monitoring plan.
|
Cues are the presence of quantified criteria and monitoring protocols rather than tone.
|
Casual
| 5
|
Running a short project and wants quick, easy-to-follow help creating a concise risk register. Likes friendly, plain-English explanations with concrete steps and minimal jargon. Uses a simple spreadsheet and doesn't want anything too stiff.
|
[
"A coordinator managing a short project who seeks actionable, business-appropriate guidance for a concise risk register. Prefers a polished tone, clear structure, and concise bullet-ready steps with minimal jargon. Uses a simple spreadsheet to document items.",
"Overseeing a brief initiative and looking for succinct, well-structured direction to build a compact risk register. Values clear headings, crisp phrasing suitable for stakeholder review, and practical recommendations. Plans to capture entries in a spreadsheet.",
"Responsible for a small project and needs concise, implementation-focused advice for a short risk register. Expects polished, businesslike wording and guidance that is easy to present to management. Will record items in a basic tracker.",
"Managing a short project and requires methodical, precisely worded guidance for producing a concise risk register. Prefers complete sentences, consistent terminology, and explicit definitions for each field. Intends to maintain the register in a structured spreadsheet.",
"Leading a brief project and requests rigorously composed instructions for a compact risk register. Expects unambiguous phrasing, carefully defined terms, and a logically ordered sequence that can be audited. Will document the register using a tabular format."
] |
To prepare a concise risk register for a short project, follow these steps:
1. Identify the project scope and objectives.
2. Brainstorm potential risks associated with the project.
3. Categorize risks into high, medium, and low likelihood and impact.
4. Assign a risk owner for each risk.
5. Develop a risk mitigation plan for each risk.
6. Review and update the risk register regularly.
This will help you stay on top of potential issues and ensure the project stays on track.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What’s the best way to describe a complex architecture diagram in a short paragraph?
|
One description emphasizes the big-picture flow and purpose, another relates components to stakeholder needs, and another uses precise component names, interfaces, and constraints.
|
Perceivability appears in the level of technical nomenclature and specificity, not stylistic flourishes.
|
Casual
| 5
|
I work with architecture diagrams and want a quick, plain-English way to sum them up for docs. Keep it friendly and no fluff—what the parts are, how they talk, and why it matters. I prefer concrete phrases over buzzwords.
|
[
"I work with architecture diagrams and need concise, polished summaries for documentation. Focus on key components, interactions, and purpose, using clear and precise wording. Keep the paragraph refined and to the point.",
"I document architecture diagrams and want succinct, well-structured summaries. Highlight major components, how they interface, and the overall objective, using crisp, businesslike language. Avoid slang and verbosity.",
"I routinely describe complex architecture diagrams in short write-ups. Use clear, refined language that outlines components, data flow, and rationale in one cohesive paragraph. Keep it concise and organized.",
"I require a rigorously composed paragraph describing complex architecture diagrams for documentation. Employ precise technical terminology and complete sentences to define components, interfaces, and data pathways. Maintain an unambiguous, exacting tone.",
"For documentation, I prefer a strictly precise description of architecture diagrams. Provide a concise yet comprehensive account of principal modules, their responsibilities, and interconnections, using standard technical vocabulary. Ensure grammatical rigor throughout."
] |
To describe a complex architecture diagram in a short paragraph, focus on the key components, their relationships, and the flow of data or processes. Use simple language and avoid technical jargon. You can break down the diagram into smaller sections, highlighting one or two key features per section. This will help readers understand the overall structure and how the different parts work together.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How should I communicate that a feature will slip by one week?
|
One message is direct with reassurance and next steps, another frames impact and mitigation, and another documents scope, new date, and approval path.
|
Differences lie in the inclusion of formal elements like approvals and scope notes versus practical messaging.
|
Professional
| 5
|
A team member who regularly updates colleagues and stakeholders on project timelines. Prefers clear, concise messages with a courteous tone and standard business phrasing. Avoids slang but keeps communication approachable and solution-oriented.
|
[
"Collaborates closely with coworkers on day-to-day tasks and shares updates in a chatty, friendly way. Uses contractions, plain language, and light, upbeat phrasing. Avoids formalities and keeps messages informal and approachable.",
"Communicates with teammates like in a hallway conversation. Keeps notes short, personable, and relaxed, favoring simple words and a friendly vibe. Comfortable with informal openings and quick sign-offs.",
"Prefers quick, conversational updates to the group. Leans on everyday language and a warm tone, skipping corporate jargon. Keeps messages breezy and down-to-earth.",
"Coordinates timeline communications with internal and external stakeholders using precise, carefully structured wording. Writes in complete sentences without contractions and chooses formal salutations and closings. Emphasizes clarity, accuracy, and professionalism in every message.",
"Prepares structured notices about schedule changes with meticulous grammar and terminology. Uses respectful greetings, full sentences, and explicit dates and contingencies. Maintains a polished, strictly professional register at all times."
] |
I recommend updating the team and stakeholders that the feature will be delayed by one week. This will help manage expectations and allow for a smooth adjustment to the new timeline. Please consider sending a notification or update to the relevant parties as soon as possible.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Outline a brief that will help an analyst provide a focused market snapshot.
|
One brief lists key questions and timeframe, another adds data sources, segments, and success measures, and another defines methodology, exclusions, and deliverable format standards.
|
Signals include methodological definitions and standards rather than overt tone.
|
Casual
| 5
|
A friendly communicator who prefers plain English and a relaxed tone. Appreciates approachable wording with contractions and a human touch. Avoids buzzwords and keeps the language easygoing and clear.
|
[
"Communicates in a polished, business-appropriate tone. Prefers concise, objective phrasing and consistent terminology while staying approachable. Avoids slang and overly casual expressions.",
"Values a crisp, executive-ready voice. Expects neutral, succinct wording suitable for stakeholder circulation. Maintains a respectful tone without sounding stiff.",
"Seeks a well-composed, workplace-ready register. Uses clear, measured language with occasional contractions acceptable. Keeps phrasing professional and focused.",
"Requires precise, grammatically rigorous language throughout. Uses complete sentences, no contractions, and exact terminology. Maintains a strictly professional register.",
"Prefers a formal, academic-style tone with unambiguous phrasing. Expects careful definitions and consistent usage of terms. Avoids colloquialisms and conversational fillers."
] |
A brief market snapshot should include key statistics, trends, and insights that provide a clear understanding of the current market landscape. This can include data on market size, growth rate, customer demographics, and competitive landscape. The analyst should also highlight any notable trends or shifts in the market, and provide recommendations for how businesses can adapt to these changes.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What’s an effective way to capture lessons learned during a fast-moving initiative?
|
One suggests a quick retrospective with simple prompts, another adds themes, owners, and follow-ups, and another standardizes categories, evidence, and validation dates.
|
Perceivability comes from evidence requirements and validation cadence versus conversational prompts.
|
Professional
| 5
|
Works on fast-moving initiatives and prefers clear, structured guidance. Values concise, actionable recommendations with brief rationale and examples. Comfortable with business-appropriate language that avoids unnecessary jargon.
|
[
"Moves fast on projects and likes straight talk. Prefers quick, skimmable tips with clear takeaways and next steps. Keep it friendly and easygoing.",
"Often juggling rapid-fire work and wants advice that gets to the point. Short, punchy notes with real-world pointers are ideal. Plain talk over formalities.",
"Running at a busy pace and appreciates no-nonsense pointers. Bullet-sized tips and simple language make it easier to act quickly. Keep the language light and straightforward.",
"Engaged in time-sensitive initiatives and seeks methodical, unambiguous guidance. Prefers precise terminology, complete sentences, and clearly delineated steps. Brevity is welcome, but rigor and clarity are paramount.",
"Operates in accelerated project contexts and expects carefully structured recommendations. Values precise definitions, explicit assumptions, and formally articulated next steps. Documentation should be grammatically exact and free of colloquialisms."
] |
Regularly schedule retrospectives to discuss successes, challenges, and areas for improvement. Use a structured format to capture key takeaways, and document them in a centralized repository for future reference.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Propose a short template for cross-team dependency tracking.
|
One template includes who/what/when, another adds risk level, status, and contact, and another enforces fields for SLA, change history, and escalation path.
|
Cues are in field rigor and governance elements rather than explicit register.
|
Professional
| 5
|
A cross-functional collaborator who coordinates dependencies between teams. Prefers clear, concise updates with a polished, businesslike tone suitable for stakeholders. Values structured, action-oriented communication that remains approachable.
|
[
"Works across squads on shared deliverables. Likes friendly, conversational updates with contractions and everyday phrasing. Comfortable with quick, relaxed notes as long as the essentials are covered.",
"Partnering with multiple teams to track handoffs. Favors a laid-back, chatty style that sounds like a hallway conversation. Keeps language simple and down-to-earth.",
"Coordinates cross-team timelines and blockers. Prefers a relaxed voice with contractions and friendly sign-offs. Not overly strict about grammar when the message is clear.",
"Manages interdepartmental dependencies and milestones. Expects precise, grammatically rigorous communication with complete sentences and no contractions. Values exact terminology and carefully structured sections.",
"Oversees dependencies across groups and reviews progress. Prefers meticulously composed messages with elaborate sentence structure and precise terminology. Prioritizes fully articulated statements and unambiguous phrasing."
] |
Here is a short template for cross-team dependency tracking:
1. Team A
* Task: [Task description]
* Dependency: Team B
* Status: [Status]
2. Team B
* Task: [Task description]
* Dependency: Team A
* Status: [Status]
This template provides a simple and structured way to track dependencies between teams, making it easier to identify and manage potential roadblocks.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How do I explain a model’s limitations to non-technical stakeholders in a short brief?
|
One explanation uses relatable analogies and plain constraints, another ties limitations to decisions and metrics, and another defines assumptions, error bounds, and validation scope.
|
Perceivability is in inclusion of formal definitions and quantitative bounds versus approachable framing.
|
Formal
| 5
|
A stakeholder-facing contributor who prepares short briefs for non-technical audiences. Expects precise, grammatically rigorous language with complete sentences and accurate terminology. Avoids colloquialisms and prefers a tightly structured, polished presentation.
|
[
"A stakeholder-facing contributor who prepares short briefs for non-technical audiences. Prefers polished, business-appropriate language that is clear, direct, and respectful. Favors concise structure without sounding stiff, with minimal unexplained jargon.",
"A stakeholder-facing contributor who prepares short briefs for non-technical audiences. Likes conversational, friendly phrasing with contractions and approachable examples. Comfortable with a relaxed tone as long as the message stays clear and concise.",
"A stakeholder-facing contributor who prepares short briefs for non-technical audiences. Seeks a confident, executive-ready tone: crisp sentences, plain terms, and a logical flow. Avoids slang while keeping the voice natural and accessible.",
"A stakeholder-facing contributor who prepares short briefs for non-technical audiences. Wants the write-up to sound like a real conversation—simple wording, contractions, and everyday comparisons. Keeps it light while staying on point.",
"A stakeholder-facing contributor who prepares short briefs for non-technical audiences. Appreciates a refined, businesslike voice with straightforward explanations and clearly labeled sections. Prefers concise wording and gentle, non-technical phrasing over formality."
] |
To explain a model’s limitations to non-technical stakeholders in a short brief, focus on the key constraints and potential biases. Clearly define the model’s scope and intended use, highlighting any assumptions or simplifications made during development. Use analogies or metaphors to help non-technical stakeholders understand complex concepts, and provide concrete examples to illustrate the model’s limitations. Emphasize the importance of transparency and accountability in AI development, and outline any plans for ongoing evaluation and improvement.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Suggest a way to align on scope when a request keeps expanding.
|
One approach proposes a simple scope statement and recap, another adds objectives, trade-offs, and change impact, and another formalizes criteria, approval gates, and change control.
|
Differences lie in control mechanisms and explicit criteria versus conversational alignment.
|
Professional
| 5
|
I prefer polished, workplace-ready communication that is courteous and direct. Clear structure, actionable wording, and a concise tone help me move quickly without sounding stiff.
|
[
"I like straight talk and a friendly vibe. Keep it simple, use contractions, and skip the stiff wording.",
"Think chat-message style—conversational, upbeat, and easygoing. Plain words over corporate-speak, please.",
"I’m good with a relaxed tone and everyday language. Short, punchy lines work great; no need for overly stiff wording.",
"Please present information with precision and complete sentences. Avoid slang and maintain an objective, courteous tone.",
"Use meticulous wording, proper punctuation, and careful structure. Colloquialisms and overly familiar phrasing are unwelcome."
] |
To align on scope, let's establish a clear understanding of the project's objectives and key deliverables. This can be done by identifying the core requirements and prioritizing them. We can then break down the scope into manageable tasks and regularly review progress to ensure we're on track. If the request continues to expand, it may be necessary to reassess the project's feasibility and adjust the scope accordingly.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What should a concise onboarding plan for a new teammate include in their first week?
|
One plan centers on essentials and quick wins, another includes goals, stakeholders, and checkpoints, and another adds formal access lists, compliance steps, and documented outcomes.
|
Signals include presence of compliance and documented milestones rather than tone markers.
|
Casual
| 5
|
I’m bringing on a teammate next week and want a short, no-fluff plan. Make it clear and practical, with goals, quick wins, and simple check-ins.
|
[
"I need a concise first-week onboarding plan for a new team member. Please include clear goals, early milestones, and scheduled check-ins.",
"Requesting a succinct first-week onboarding plan for a new hire. Outline defined objectives, initial milestones, and planned check-ins.",
"I require a precise first-week onboarding plan for a new colleague. Specify objectives, early milestones, and scheduled review meetings.",
"Please provide a rigorously structured first-week onboarding plan for a new staff member. Include explicit objectives, initial milestones, and formal check-ins.",
"Kindly prepare a concise, comprehensive plan for a new employee’s first week. Detail objectives, initial milestones, and scheduled progress reviews."
] |
A concise onboarding plan for a new teammate should include clear goals, quick wins, and simple check-ins. Here\'s a suggested outline for their first week: \n\nDay 1-2: Introduction and Goal Setting\n- Introduce the teammate to the team and the company\n- Set clear goals for their first week and month\n\nDay 3-4: Quick Wins\n- Assign tasks that provide a sense of accomplishment and progress\n- Encourage collaboration and feedback\n\nDay 5-7: Check-ins and Feedback\n- Schedule regular check-ins to discuss progress and provide feedback\n- Encourage open communication and address any concerns\n\nThis plan provides a structured approach to onboarding, allowing the new teammate to quickly get up to speed and feel comfortable in their new role.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How do I close a meeting when we didn’t reach a decision?
|
One close summarizes key points and next steps, another assigns owners, deadlines, and follow-ups, and another records open issues, decision criteria, and approval process for next time.
|
Perceivability comes from formalization of decision criteria and documentation versus simple recap.
|
Formal
| 5
|
Prefers to close discussions with precise, courteous phrasing that maintains professional distance. Uses complete sentences, avoids contractions, and clearly states follow-up actions and timelines. Emphasizes clarity and decorum in all closing remarks.
|
[
"Favors a polished, business-appropriate tone that’s clear and concise. Uses courteous phrasing, some contractions, and focuses on action items and ownership without sounding stiff.",
"Keeps language executive-ready but approachable. Summarizes key points, confirms owners and deadlines, and uses straightforward, respectful phrasing.",
"Leans toward friendly, conversational language with contractions and a relaxed vibe. Closes by recapping what’s next and who’s doing what, keeping it upbeat and approachable.",
"Uses everyday phrasing, light encouragement, and a warm tone. Keeps closings short, uses first names, and suggests next steps without formalities.",
"Communicates like a teammate chatting in Slack—informal, direct, and friendly. Wraps up with a quick recap, casual sign-off, and a nudge on next steps."
] |
It is generally recommended to close a meeting without a decision by summarizing the key points discussed, expressing appreciation for the participants
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
Outline a process for triaging inbound requests so that urgent items get handled first.
|
One process uses simple priority buckets, another adds service levels and routing, and another defines criteria, thresholds, and audit logs.
|
Differences appear in precision of thresholds and record-keeping rather than overt language style.
|
Professional
| 5
|
A project coordinator who values polished, business-appropriate communication. Prefers clear, concise guidance that can be shared with stakeholders. Seeks actionable steps stated in a confident, respectful tone.
|
[
"Handles general requests and likes a relaxed, conversational tone. Comfortable with plain language and friendly phrasing. Appreciates straightforward explanations without stiff wording.",
"Juggles everyday tasks and prefers an easygoing voice. Likes concise, down-to-earth wording with contractions. Finds upbeat, approachable language most helpful.",
"Supports a small team and favors informal, human-sounding messages. Prefers simple phrasing and a friendly vibe. Encourages a talk-like-you-type style.",
"Coordinates intake and prefers precise, strictly grammatical language. Expects complete sentences and careful word choice. Values formality and decorum in written guidance.",
"Oversees request routing and expects rigorously composed prose. Prefers unambiguous terminology and fully articulated statements. Avoids colloquialisms and contractions."
] |
To triage inbound requests, follow these steps: 1. Identify the urgency of each request based on its priority and deadline. 2. Sort the requests in order of their urgency, with the most urgent ones first. 3. Assign a team member or task to each request, considering their workload and availability. 4. Set deadlines for each request and track progress. 5. Regularly review and adjust the triage process as needed to ensure it remains effective.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
How should I communicate a tentative idea to leadership without over-committing?
|
One approach shares the concept with a caveat and a small next step, another frames potential impact and assumptions, and another documents hypothesis, evidence plan, and decision gates.
|
Cues include the level of hypothesis formalization and decision checkpoints versus casual floating of ideas.
|
Formal
| 5
|
I prepare communications with precise language and complete sentences. When addressing senior leadership, I favor structured messages, explicit qualifiers, and carefully bounded commitments. I seek guidance on presenting a preliminary concept while maintaining clear caveats and risk disclosures.
|
[
"I communicate in a polished, business-appropriate tone aimed at clarity and efficiency. I want advice on floating an early concept to leadership while setting proper expectations and boundaries.",
"My messages are clear, courteous, and tailored for senior audiences. I'm looking for a practical way to share a nascent idea with leaders without implying timelines or firm commitments.",
"I like to keep things conversational and straightforward. I’m trying to float an early idea to the higher-ups without making it sound like a promise.",
"I usually explain things in plain, friendly language with a light touch. I want help sharing a rough concept with leadership so it doesn’t come off as locked in.",
"I tend to talk in a relaxed, approachable way and keep things simple. I’m looking for a way to toss out an idea to leaders without painting myself into a corner."
] |
I recommend presenting the concept as a preliminary idea, emphasizing that it is still in the early stages of development and subject to further refinement. This can be done by using phrases such as “exploring the possibility of,” “considering the potential for,” or “looking into the feasibility of.” Additionally, it may be helpful to highlight the potential risks and challenges associated with the idea, as well as any areas where further research or analysis is needed. By taking this approach, you can effectively communicate the idea without over-committing to its success or feasibility.
|
communication_formality
|
[
"Casual",
"Professional",
"Formal"
] |
Controls the tone and register of communication. Casual users prefer conversational language with contractions and friendly expressions. Professional users expect polished, business-appropriate language without being stiff. Formal users require precise, grammatically rigorous language with complete sentences and professional terminology.
|
What’s a good pattern for reporting progress in a daily update with limited time?
|
One pattern stresses brief highlights and blockers, another ties updates to objectives and deadlines, and another uses standardized fields, timestamps, and references.
|
Perceivability lies in standardization and traceability over narrative brevity or friendly tone.
|
Casual
| 5
|
I send a quick daily check-in and I’m usually short on time. I’d love a simple, no-fuss way to share what I got done, what I’m doing next, and anything in my way.
|
[
"I provide a concise daily update and often work within tight time limits. I am looking for a clear, repeatable structure to communicate completed work, upcoming tasks, and any blockers efficiently.",
"I share a brief status update each day with limited time available. I would appreciate a straightforward template to outline progress, next steps, and blockers.",
"I need to deliver a quick daily summary due to schedule constraints. I seek a clean, business-appropriate format to highlight accomplishments, upcoming work, and blockers.",
"I submit a brief daily status report under strict time constraints. I require a succinct, well-structured framework for conveying completed deliverables, planned activities, and impediments.",
"I prepare a short daily update with limited time available. I request a precise, disciplined pattern for reporting accomplishments, forthcoming tasks, and any obstacles."
] |
Share 3-5 key accomplishments, mention 1-2 upcoming tasks, and highlight any obstacles or challenges that need attention.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.