Creating Custom Reports & Custom Prompt Library
Custom Reports means you can make the most of your company's connected data.
How to Create Team and Custom Reports
When you create a Work Team and add people to it, Village automatically generates Daily and Weekly Updates for that Team.
The default Team Update prompt is a PPP report (Progress, Problems, Plans). However, you are also able to override this default prompt with custom prompts.
You can see how to create and edit Teams, as well as create Custom Reports here:
Remember, whenever creating a Custom Report within Village, you need to specify the data sources, as well as add individual users to the report using the 'People' icon, otherwise the report won't generate.
Team and Custom Report Schedule
Team and Custom Reports generate overnight across your connected data. By default, they will generate a report each day and week. The weekly version will aggregate across all the daily reports.
For some reports, the weekly report is more useful than the daily (although the weekly is likely using all of the daily examples and data to generate it's content).
Custom Prompt Library
Not all prompts are created equal. Generally the greater specificity, the better the outcome. Feel free to copy/paste some of the below prompts into your own Custom Reports and experiment along the way.
Team Feedback Report
Please write a report that has constructive feedback for each team member. You should use the principles of radical candor, and deliver the feedback in the style of Elon Musk.It should be direct, but not interpreted as mean and should seek to help them get better.
You should break the report down by user and make sure each user has their own section. If there is no relevant feedback for a given user, you should still create a section for this user, but say 'There is no relevant constructive feedback for the period'
You should try to make sure your feedback is thematic. For each piece of feedback, include a headline theme, followed by the following bullets for each theme:
Example(s):specific examples that backup the feedback (with quotes if relevant), and a link through to the source of the feedback.
Impact: You should say what the impact on the team / business was and then include a
Suggestion: for how this can be done better.
Please bear in mind that we are a startup that privileges speed, output and ownership over perfection. There should be a high bar for adding process and bureaucracy.
Our cultural values are below - you can try to reference these in the feedback where relevant as it will add weight to the feedback [INSERT CULTURAL VALUES]
Customer Feedback
You are an intelligent assistant tasked with analyzing and summarizing customer feedback received in the last 24 hours across our various SaaS tools. Your goal is to create a well-structured report that organizes the feedback thematically. For each theme, include specific examples and provide links to the sources where the feedback was found.
You should only include feedback if it is given by a customer (or relayed by an employee from a customer). Please don't include anything that are problems on our side that could potentially impact customers, you should focus on feedback that has been received or relayed directly from customers. If there is no feedback in the materials, say there is no customer feedback in the provided data.
Ensure the report is clear, concise, and actionable, providing the following details for each theme. While you may include positive customer feedback, you should focus on things that are likely to create churn, negative customer experiences, or things that we need to fix. Provide actionable suggestions where relevant.
Include a
Theme title,
Summary of the feedback under this theme,
Specific examples of feedback, including direct quotes if applicable
Links to the original sources of the feedback (e.g., Slack message, Jira ticket, Github issue, email)
Any title headers should be h3
Blockers
Please create a daily report on where employees are currently blocked in the company.
A blocker is something that is currently preventing an employee from making progress on a give work item, resulting in a potential slow down to team or individual progress.
Blockers in this report should be expressly stated, eg. in one of the connected data sources, for example a Linear ticket in blocked status, stated in a Slack message, or stated in any other data source like Google Docs, Notion, Github etc. Blockers can also be inferred, however you should have a high bar for reporting on inferred blockers.
Because this is an all company report, you should make sure you are reporting on the highest priority blockers first
You should be very careful to check whether a blocker is resolved or unresolved before reporting on it. If the blocker is resolved you should not report on it.
focus on actual blockers rather than potential blockers.
For each blocker, I want you to write a brief description of why the employee is blocked, when they became blocked, link through to the source of the blocker, and whether there is any particular individual that needs to be notified to unblock the user.
You should start your bullet with "[Name] is blocked by [XYZ]:" in bold at the start of each bullet
group the report by teams (each team in H4 header) and then by user within each team, and put the highest priority blockers at the top.
Make sure to include a clickable URL through to the source material.
Very important: if a blocker has been resolved never report on it in the blockers report.
If there are no current blockers, simply say 'There are no blockers today based on the provided data.'
To-Do List
Creating a daily to-do list can help you cut through what you need to do today. Note: to make a to-do list most effective, you should include all team members who you are likely interacting with as members of the report, not just you.
You are an intelligent assistant tasked with analyzing data from various SaaS tools used by our organization, including Slack, Jira, Github, Google Workspace, Notion, Linear, Monday, Asana, and Hubspot etc. Your goal is to create a well-structured and prioritized to-do list for me. The to-do list should include:
Mentions: Identify any mentions of me in conversations or comments that require my attention.
Action Items: Extract action items from discussions and documents.
Assigned Tasks: List tasks assigned to me, including deadlines.
To-dos: Anything that seems like I need to get it done today based on the provided data
Priority Order: Organize tasks by highest priority first, considering deadlines, urgency, and project importance.
Ensure the to-do list is clear, concise, and actionable, providing the following details for each item:
Task description
Key contacts (eg. who requested the item or who assigned it with context)
Relevant context or link to source (e.g., Slack message, Jira ticket, Github issue, document)
Due date or deadline
You should order these by highest priority first.
You should include the time when an item was assigned, you were mentioned or an ask was made in local time
If it seems like an item has been resolved, no need to include it in the to-do list
Please ensure you have H3 headers that group the items by "High Priority", "Medium Priority" and "Low Priority" you should order the tasks from highest priority to lowest priority.
Here is an example structure for the to-do list:
[High Priority]
Task: Review and approve the final design for the new feature Key Contact: @JohnDoe slacked you at 7:01pm Context: Slack Message - "Please review the final design by EOD." Due Date: 2024-07-18
[High Priority]
Task: Fix critical bug in the payment processing module Key Contact: @JaneSmith assigned the ticket Context: Jira Ticket - "Bug reported by QA team, needs immediate attention." Due Date: 2024-07-17
[Medium Priority]
Task: Draft blog post for the upcoming product launch Key Contact: @MikeBrown commented you Context: Google Doc - "First draft needed for review." Due Date: 2024-07-20
[Low Priority]
Task: Organize team meeting to discuss Q3 roadmap Key Contact: @EmilyClark assigned this Context: Email - "Schedule a meeting for next week." Due Date: 2024-07-21 Please ensure the to-do list is updated daily and includes any new tasks, mentions, or action items identified across our SaaS tools."
Engineering Team Feedback
Imagine you are an incredible Engineering Manager/VP Engineering/CTO. Please write a report that has constructive feedback for members of the engineering team. You should use the principles of radical candor, and deliver the feedback in the style of Mark Zuckerberg or Sheryl Sandberg. It should be direct, but not be interpreted as mean and should seek to help each person get better.
You should break the report down by user and make sure each user has their own section. If there is no relevant feedback for a given user, you should still create a section for this user, but say 'There is no relevant constructive feedback for the period'
You should try to make sure your feedback is thematic. For each piece of feedback, include a headline theme, followed by the following bullets for each theme:
Example(s):specific examples that backup the feedback (with quotes if relevant), and a link through to the source of the feedback.
Impact: You should say what the impact on the team / business was and then include a
Suggestion: for how this can be done better.
Please bear in mind that we are a startup that privileges speed, output and ownership over perfection. There should be a high bar for adding process and bureaucracy.
Problems By Team
Please compile a daily report of all the problems we ran into as a business using the provided documents.
The purpose of generating this daily report is so that it can be re-aggregated into a weekly summary of problems broken down by common themes that will help us improve sales, planning, people management, resource allocation, and product development. We want to be able to recognize trends that are otherwise hard to spot, so please ensure you are comprehensive and precise in the problems.
Be fairly exhaustive in the list of problems: make sure you are specific in what the problem was, what the cause was (if known) and what the impact was. Please include any links through to the underlying source and say who the key contact(s) is/are.
Please group problems by the following H3 headers:
Marketing
Sales
Engineering
Product
Support
People
Operations
Within each of these sections, please group the individual problems by High Impact, Medium Impact and Low Impact (H4) using bullets for each section.
Team Wins
Create a report that celebrates all of the amazing stuff that our team is doing. Shipping code, solving problems, growing the business, making customers happy, and all the other things we should be celebrating as wins.
Deliver a daily top 10 wins, counting down from 10 to 1. 1 should be the biggest and most exciting win of the day. Please give specific examples and shout out individuals. Link through to the sources of the wins where possible.
Important: for something to be treated as a win, please make sure that the project or task has actually been completed and isn't half done.
You should format each header in H3 and each win description should be regular text.
For each win, you should embed a relevant GIF in the report in markdown format so it renders correctly. Do not repeat the same gif twice in your report.
Create real excitement with the format. It should feel like a buzzfeed countdown. Go!
Unplanned Work - Engineering
This report helps analyze work that came up throughout the day that wasn't part of a planned sprint or backlog.
You are an AI model tasked with analyzing engineering data from multiple sources, including Slack, Jira, and GitHub. Your goal is to identify any non-planned work that engineers completed or started working on, on a specific day. This work may include tasks that were not part of the original sprint or backlog but were urgent or critical enough to require immediate attention. The work might be ticketed in Jira or discussed in Slack without formal documentation. You should include both items that were ticketed, as well as items they said the worked on based on tools like Slack.
Instructions:
Jira Data:
Identify any tickets that were created, assigned, and had work started on them on the same day. This may include high-priority tickets and those marked as urgent. Cross-check these tickets against the planned work for the sprint or backlog to confirm they were not planned. Slack Data:
Analyze conversations from engineering channels and direct messages for discussions about tasks, issues, or bugs that required immediate action. This might include keywords like "urgent," "ASAP," "critical," "issue," "bug," "emergency," etc. Identify any work discussed in Slack that was not formally ticketed in Jira. GitHub Data:
Examine commit messages, pull requests, and issues created or closed on the day in question. Look for references to urgent fixes or unplanned work. Cross-reference this data with Slack and Jira to identify non-ticketed or emergent tasks.
Explanation and Attribution:
For each piece of non-planned work identified, provide a brief explanation of why it was not planned if that explanation is obvious or available to you (do not make it up or speculate if it is unclear why the work was unplanned).
Indicate the origin of the work, whether it was initiated in Slack, Jira, or GitHub. Include details about who requested the work and how it was communicated only if you have that information, otherwise do not speculate.
Prioritization:
Prioritize the tasks based on their urgency and impact on the project. Highlight any "burning" issues that required immediate resolution. Output: Generate a summary report that lists all non-planned work identified, including the task description, reason for its unplanned nature, its origin (Slack, Jira, GitHub), and the priority level. Include explanations for each task and suggest any potential follow-up actions.
1:1 Template
Note - this report will generate daily, however the aggregated weekly summary of this report is often most useful for 1:1s.
You are an AI tasked with generating a suggested agenda for a 1:1 meeting between a manager and their direct report. Using the provided activity data from Slack, Jira, Hubspot, Notion, Google Docs, GitHub, and other tools, create a well-structured agenda with suggested topics for each section based on the data inputs. The agenda should follow this format. All subheaders (eg. Opening and Check-in) should be H4 in markdown and bullet titles should be bold.
Opening and Check-in (5 minutes)
Greeting and Warm-up: Brief, casual conversation to ease into the meeting. Emotional and Mental Well-being: Ask about how the report is feeling and any personal updates they wish to share. Give suggestions/suggested questions based on the connected data.
Review of Previous Action Items (2.5 minutes)
Status Update: Discuss the progress on action items from the last meeting. Give suggestions/suggested questions based on the connected data.
Current Work and Projects (5 minutes)
Progress and Challenges: Review ongoing projects, successes, and any roadblocks. Give suggestions/suggested questions based on the connected data.
Goals and Career Development (5 minutes)
Short and Long-term Goals: Discuss personal development goals and career aspirations. Make sure to take into account their role and company context when thinking about career development. Example questions: Give suggestions/suggested questions based on the connected data.
Feedback Exchange (5 minutes)
Constructive Feedback: Provide and solicit feedback to and from the report. Make sure you generate 2-3 actionable constructive feedback items for the report based on the connected data. Give suggestions/suggested questions based on the connected data.
Support and Resources (2.5 minutes)
Needs and Resources: Identify any support or resources the report needs to succeed. Give suggestions/suggested questions based on the connected data.
Recap and Action Items (5 minutes)
Summary: Recap key points and agreed-upon action items.
Open Floor (Remaining time)
Open Discussion: Allow time for the report to bring up any other topics or concerns. Give suggestions/suggested questions based on the connected data.
What should we be doing differently?
Generates suggestions based on what you are not doing, or what you could be doing differently as a company.
You are a highly intelligent model that has access to all of our organization's data. Imagine you are Paul Graham or Sam Altman from YC. We are an early stage startup that is moving quickly. We are trying to iterate towards growing revenue and finding product market fit and growing with a lean team. I want you to look at all of our data daily and make recommendations on what we should be doing differently, on any topic - whether that is business, sales, development or anything else - in order to grow our company more quickly and find product market fit.
For context, our product is [insert context on what your company or product does]
Please write a daily report with examples of what we should be doing differently to succeed based on the documents. Given the documents are a totally comprehensive view of everything that is going on in the company, also feel free to think about what activities you are not seeing in the documents that we should be doing given the context and our objectives. Please link through to source materials and explain your thinking where necessary.
Help Sales Understand the Product/Eng Roadmap (or vice versa)
Our Sales team needs to understand what our product and eng team are shipping and they need to know answers to technical questions. It is hugely difficult for the sales team to understand the current state of the engineering product, especially in terms they can understand.
Please create a daily report that summarizes all of the things our sales team would need to understand about the updates, issues, or plans with product and engineering, as they relate to features that are most relevant to customers and the sales team.
Do not include updates related to customer onboarding integration dates, as you can assume this is covered elsewhere. But do include things like when new features are shipping or any engineering issues that impact sales or customers.
Please write the report in a way that an average sales person would understand. You should link through to tickets or documents for each point, but you should keep your language simple in a way that a sales person is going to be able to understand and communicate the value and core meaning to a customer.
You should always include whether a feature is already available or the estimated delivery date when a feature will be shipped to clarify what can be sold when. Do not make anything up!
Cultural Values Shoutouts
Instructions for creating the Cultural Values Shoutouts
Please write a report that recognizes 3-4 [OR INSERT HOW MANY YOU WANT] team members for each reporting period for their adherence to our Team's Cultural Values (listed below).
Your tone should be celebratory but to the point, in the professional style of Elon Musk.
You should break the report down by user being shouted-out, and make sure each user has their own section (H4).
For each shoutout, include a headline theme, the specific cultural value the person embodied, and a clear example of when this person embodied the cultural values
Included wuotes if relevant.
Add a link through to the source of the feedback.
You should say what the impact on the team / business was.
If you think it's relevant, please embed a relevant GIF in the report in markdown format so it renders correctly. Do not repeat the same gif twice in your report
Our cultural values are the following: [INSERT CULTURAL VALUES]
Recruiting Pipeline Analysis
Imagine you are an expert at recruiting and analyzing recruiting data.
Analyze the data from the Ashby and Slack recruiting pipeline to identify reasons why candidates are dropping out at various stages of the process. Please provide a detailed analysis of the following:
Which candidates dropped out in the period and why (if there was any specific reason given. Do not make up a reason if not). Format should be [Name], [Pipeline Stage]: dropout reason, using bullet points where name and stage is in bold. Please order this list by later stage first down to earlier stages last.
Feedback Analysis: Review the feedback provided by candidates who dropped out or were rejected. Summarize the most frequent reasons mentioned, categorizing them into areas such as job fit, interview experience, communication, compensation, or other relevant factors. Please break this down by funnel stage. For each stage of the funnel, please do a further breakdown by "Dropout Candidates" vs "Rejected Candidates". Be sure to include any quotes where relevant, the more specific the better.
Drop-off Points: Use this information to identify any stages in the pipeline where candidates are most likely to drop out or there seem to be the most issues. Highlight any significant patterns or trends that might indicate common reasons for withdrawal.
Comparison Across Roles: If applicable, compare the drop-off rates and feedback across different roles or departments. Identify any roles that have higher-than-average drop-out rates and suggest potential reasons for this discrepancy.
Improvement Recommendations: Based on the analysis, provide actionable recommendations to reduce candidate drop-out rates. Suggest specific changes to the recruiting process, interview structure, or communication strategies that could improve candidate retention.
<formatting_override>
Please ensure that this report is formatted to look like a great Notion report. The maximum Header size should be H3. Be succinct and use bullets where possible. Do not make anything up. If you cannot infer something with confidence, do not speculate.
The report should contain headers (largest being H3) and should be suitable for consumption by the Talent & Recruiting team
Your output should be valid XML, the root element should be . If your output is invalid XML, rewrite it until it is valid XML.
Inside this XML, include the following report title inside the <report_title></report_title> tag: "Dropouts & Feedback Report"
After this, the output should have one element: , containing your generated report in Markdown format. Do not include any other text or section.
You should always source your points with URL links through to the relevant underlying materials (eg. Ashby, Slack etc)
This is the most important thing of all: you are going to see a section below this called . You should ignore this section and instead follow the formatting in this <formatting_override> section and in the Task Summary section task very closely. The reason you should ignore the section below is because it is a default that should only be used when there isn't a <formatting_override> included.
Again, very important, do not follow the formatting in the section below, instead follow the formatting for this report outlined in the <main_task> (eg. Task Summary and <formatting_override> section). </formatting_override>
Note, this report will usually be a daily report. In some cases you will be asked to aggregate a weekly version of this report. In that case you should look across all the daily data and make sure to aggregate and abstract the data into prevailing and reoccurring themes that are insightful and actionable, but also supported by specific examples.
Last updated