One Pager Draft

Chilla

Description: What is it?

Chilla is a Slack integration bot that helps product managers find the right people, schedule meetings efficiently, and follow up on deliverables easily.

Problem: What problem is this solving?

We are driven by the goal to cut down wasted time that inhibits productive cross-functional collaboration. We want to get to prioritization and alignment faster without losing the warmth of human connection. 

Why: How do we know this is a real problem and worth solving?

9/15 of the PMs we interviewed raised the issue of struggling with cross-functional collaboration. This includes complaints around different teams having different objectives, outdated documentation and internal profiles, and not knowing the right person to talk to.

Success: How do we know if we’ve solved this problem?

We know we have solved this problem when we meet our objective of making cross-functional collaboration and 1:1 discovery completely frictionless, outpacing competitors by transforming team coordination into an intuitive, empowering experience. Through our pilot tests, we aim to validate consistent weekly adoption, while slashing average scheduling turnaround time from over 48 hours to under 4 hours. We will measure precision and user trust by achieving an above 85% confirmed talent match rate within two clicks alongside over 80% positive sentiment on bot nudges, keeping notification mute rates below 5%. Ultimately, hitting a 40% organic expansion rate, where pilot PMs proactively add the bot to new cross-functional channels or refer other team leads, will confirm that our product delivers clear, self-sustaining value.

Audience: Who are we building for?

We are building for PMs in a mid to large sized tech company, focusing on connecting a company with rich internal profiles and scheduling features. This would involve companies who have over 100 employees.

What: Roughly, what does this look like in the product?

Chilla lives in Slack and supports three connected workflows:

  1. Find a collaborator. A PM asks, “Who can help with onboarding analytics?” Chilla suggests relevant people, explains each match, and links to the supporting information. Profiles include expertise, team, current responsibilities, and when information was last verified. Employees can fill out more information on their profiles.
  2. Coordinate a meeting. After the PM chooses a person to meet with, Chilla proposes available times through a connected calendar. The PM reviews the invitation and agenda before it is sent.
  3. Follow up on commitments. A PM records an agreed deliverable, owner, and due date. The owner confirms the commitment, and Chilla provides configurable reminders and a shared status view.

How: What is the experiment plan?

For our experiment, we will create three test cards testing desirability, financial viability, and feasibility. We will also create learning cards for each test after conducting experiments. For desirability, we hypothesize that employees will prefer to use Chilla over existing methods to find collaborators, such as asking colleagues or manually checking calendars. To test this, we will give users a realistic scenario where they are tasked to find someone from another team with relevant experience. We will first ask how they would normally find that person, then have them use our interactive v0 prototype to complete the task. Afterward, we will ask whether they would prefer using Chilla or their existing methods. We are successful if at least 70% of users successfully find a suitable collaborator on Chilla, save time, and say they would prefer our product over others. 

For financial viability, we believe that a free trial will convert users. We will use our v0 interactive prototype to deploy an active trail with full access to internal profile querying and calendar optimization, concluding with an in-app survey prompt and exit evaluation. We will measure usability, efficiency, engagement, and if users state that they would continue using our product even after the testing period. We will be right if more than 80% of our test pool state that they will continue using our product in the big tech context. 

Our final test, in terms of feasibility, is built around the hypothesis that people are willing to opt in to share internal profile data and calendar data to where the product is useful. To verify our hypothesis, we will conduct a test inside a pilot Slack workspace by introducing a bot onboarding flow. Users will be shown permissions Chilla needs to access their relevant information (“connect your calendar” & “Show me in Chilla reccommendations”). We will record whether users approve each permission and ask users who declined what information they would be willing to share instead. We will measure the percentage of users who approve of these permissions, and we will be right if at least 25% of users approve for access, and 60% connect their calendar. These tests will help us test our core functionality and features within Chilla. 

When: When does it ship and what are the milestones?

We aim to ship our Slack integration in Week 10 of Fall Quarter. Over the next few weeks (week 9-10), our key milestones are to finish building the prototype and begin developing our pitch. We will use the upcoming break to refine the product details and polish the pitch narrative, complete user testing, and write learning cards by the middle of Week 9. We also plan to get feedback from our PM mentors. This will help us finalize everything for launch in Week 10.

One Liner from Reading: 

We chose Lenny’s 1-pager because, unlike heavier PRDs from Figma or Product Hunt that bog early exploration down in exhaustive edge cases and specs, his Airbnb-honed framework forces immediate clarity on the core problem, hypothesis, and success metrics in a single digestible page. This felt most intuitive for our product, to place it in our target market, with our metrics for success. 

About the author

Leave a Reply