Turn your meetings into actionable collaboration insights
Leanmote connects to Google Calendar & Meet to give leaders a clear view of how meetings impact team performance and costs.
Understand if meetings help collaboration or create unnecessary overhead.
Detect how much focus time teams actually preserve.
Measure meeting load, costs, and participation patterns automatically.
Back leadership decisions with data, not guesswork.
🔗 Why Leanmote for Calendar & Meet?
Google Calendar tells you when a meeting happens — but not its impact. With Leanmote, every scheduled and recurring meeting is transformed into metrics that show the real cost and efficiency of collaboration:
Time lost in recurring or large meetings.
Distribution of focus vs. meeting time.
Alignment between teams through connectivity graphs.
Early detection of overload on certain individuals or groups.
⚡ Real-Time Sync
Once connected, all meetings are automatically analyzed:
Meeting Hours – Track total time invested in meetings.
Focus Time – Measure uninterrupted time left for deep work.
Meeting Duration – Spot if meetings run too long.
Recurrent Meetings – Detect patterns that eat into productivity.
Large Meetings – Identify sessions with too many participants.
Meeting Costs – Estimate the hidden cost of meetings in work hours.
All data is updated continuously, without any manual reporting.
🌍 Benefits for Your Organization
Boost Productivity: Reduce unnecessary recurring and large meetings.
Protect Focus: Ensure deep work time isn’t fragmented.
Lower Costs: Quantify and cut down on wasted meeting hours.
Strengthen Collaboration: See how teams connect and where silos exist.
📌 Typical Use Case
A data engineering team spends 8–10 hours weekly in coordination calls. With Leanmote:
Meeting patterns are automatically tracked from Google Calendar.
Dashboards highlight that 40% of time is lost in recurring sessions.
Leaders spot overloaded connectors and reduce meeting frequency.
The team recovers focus time, improves delivery speed, and lowers coordination costs.
👉 The outcome: fewer but more effective meetings, better collaboration, and lower costs.
Turn your meetings into actionable collaboration insights
🚀 Value Proposition
Leanmote connects to Google Calendar & Meet to give leaders a clear view of how meetings impact team performance and costs.
Understand if meetings help collaboration or create unnecessary overhead.
Detect how much focus time teams actually preserve.
Measure meeting load, costs, and participation patterns automatically.
Back leadership decisions with data, not guesswork.
🔗 Why Leanmote for Calendar & Meet?
Google Calendar tells you when a meeting happens — but not its impact. With Leanmote, every scheduled and recurring meeting is transformed into metrics that show the real cost and efficiency of collaboration:
Time lost in recurring or large meetings.
Distribution of focus vs. meeting time.
Alignment between teams through connectivity graphs.
Early detection of overload on certain individuals or groups.
⚡ Real-Time Sync
Once connected, all meetings are automatically analyzed:
Meeting Hours – Track total time invested in meetings.
Focus Time – Measure uninterrupted time left for deep work.
Meeting Duration – Spot if meetings run too long.
Recurrent Meetings – Detect patterns that eat into productivity.
Large Meetings – Identify sessions with too many participants.
Meeting Costs – Estimate the hidden cost of meetings in work hours.
All data is updated continuously, without any manual reporting.
🌍 Benefits for Your Organization
Boost Productivity: Reduce unnecessary recurring and large meetings.
Protect Focus: Ensure deep work time isn’t fragmented.
Lower Costs: Quantify and cut down on wasted meeting hours.
Strengthen Collaboration: See how teams connect and where silos exist.
📌 Typical Use Case
A data engineering team spends 8–10 hours weekly in coordination calls. With Leanmote:
Meeting patterns are automatically tracked from Google Calendar.
Dashboards highlight that 40% of time is lost in recurring sessions.
Leaders spot overloaded connectors and reduce meeting frequency.
The team recovers focus time, improves delivery speed, and lowers coordination costs.
👉 The outcome: fewer but more effective meetings, better collaboration, and lower costs.
This guide will help you generate an App password in Bitbucket, which is required to integrate your Bitbucket account with Leanmote. By following these steps, you will obtain the necessary credentials to connect Bitbucket with Leanmote and enable data synchronization securely.
Step 1: Access Bitbucket Settings
Log in to your Bitbucket account.
Click on your profile avatar in the top-right corner.
Select Personal settings from the dropdown menu.
Step 2: Create an App Password
In the left sidebar, click on App passwords.
Click the Create app password button.
Enter a Label for the password (e.g., “Leanmote Integration”).
Select the necessary Permissions required for the integration:
Click Create.
Copy the generated App password and store it securely. This password will only be displayed once.
Step 3: Add the App Password to Leanmote
Log in to your Leanmote account.
Navigate to the Productivity Tools section.
Select Bitbucket Integration.
Paste the App password in the designated field.
Click Save to complete the integration.
By following these steps, you will successfully integrate Bitbucket with Leanmote and enable secure data synchronization.
With this guide, you’ll be able to integrate Jira with Leanmote to centralise key project information and enhance productivity visibility and analysis.
Required Permissions
The user generating the token must have admin access to the projects.
Endpoints Used (read-only):
Get Issues: To retrieve metada about projects, epics, and tasks in Jira.
Follow the steps below to configure your token and connect both platforms. Let’s get started! 🚀
Connecting GitHub allows us to deliver key insights in three areas:
DORA Metrics (Software Delivery Performance): Measure software delivery efficiency across Lead Time, Deployment Frequency, Mean Time to Recovery, and Change Failure Rate. These metrics are industry standards for evaluating and improving engineering performance.
Team Collaboration: Visualise how teams interact around PRs and reviews, identifying collaboration bottlenecks, response times, and workload balance.
Team Activity: Break down activity at the member level (commits, PRs created, reviews, comments) to gain a clear view of contributions and working dynamics.
🔐 Permissions Requested
All permissions are read-only. We never request write or admin access.
Metadata (read-only): to list repositories and access basic information.
Pull requests (read-only): to retrieve PRs, commits, reviews, and comments.
Contents (read-only): only required if commits exist that are not linked to Pull Requests.
📌 Endpoints Used
Endpoint
Permission
Purpose
/user/repos
Metadata: read
List user repositories for mapping in Leanmote.
/repos/{owner}/{repo}/commits
Contents: read
Retrieve commit history for metrics and timeline tracking.
/repos/{owner}/{repo}/pulls
Pull requests: read
List repository pull requests for workflow analysis.
/repos/{owner}/{repo}/pulls/{pr}/reviews
Pull requests: read
Retrieve reviews of each PR to assess participation and review times.
/repos/{owner}/{repo}/pulls/{pr}/commits
Pull requests: read
Link commits to PRs for detailed tracking.
/repos/{owner}/{repo}/pulls/{pr}/comments
Pull requests: read
Retrieve PR comments to analyze team discussions.
✅ Principle of Minimal Scope
At Leanmote we follow the principle of least privilege:
We only request read-only permissions.
We never request write or admin-level access.
Each permission is tied to a specific endpoint and a clear purpose.
At Leanmote we collect information to get to know people, understand them, and contribute to their wellbeing. Our objective is to provide the solution to companies to build better working environments in a world with growing complexities.
How we collect and interpret information
We want to get to know people, without bothering them. That’s not an easy task when they are working, focused on what they have to do, maybe meeting deadlines, and dealing with pressures.
Leanmote offers an indirect way to collect data in addition to survey insight by connecting with productivity apps- like Slack, Jira, Google Meets, Teams and more- that the company already uses.
Understanding the general data lifecycle:
Image rights: A Beginner’s Guide to Data & Analytics, Harvard EBook.
“A data project’s steps are often described as a cycle because the lessons learned and insights gleaned from one project typically inform the next. In this way, the final step of the process feeds back into the first, enabling you to start again with new goals and learnings”, A Beginner’s Guide to Data & Analytics, Harvard EBook.
Also, the value of the data improves when you connect as many apps as you can because we cross all the information. This enables Leanmote to offer a closer look to reality.
3 levels of showing data
Leanmote gives the power of managing data to every person that uses the platform.
User/Employee: sees its own data and chooses what’s shown to others.
Imagine that you are with the computer, at working hours and you receive an email from HR with a climate survey. You have to stop what you are doing, fill the form and send it. What happens with that information? Who sees it? Where does it go?
With Leanmote, you can see this information. We enlighten people with their own data first, at real-time. When you accept to complete a survey or answer a question, you can instantly check it on the dashboard. In addition, anyone can go to settings and choose what to display for other members of the company.
I complete a survey or answer a question, and instantly check it on my dashboard. In addition, everyone can go to settings and choose what to display for other members of the company.
Manager/Team Leader: each team decides how to show their information.
The manager sees the team’s information when there are four or more people on their team. Analyzing their team’s data in real-time, gives them the opportunity to unlock customized management and better lead their colleagues.
C-Level/ People and Culture Leader: sees the protected and aggregated information at every team or department level
They can access all data but they don’t have unlimited power. Everyone has the control of their own data. This level analyzes the information that each team of the company chose to give.
Our 6 ethical principles
⭐Your data is yours. We don’t share it with anyone else.
⭐You choose what to share and with whom.
⭐You connect Leanmote with your working apps.
If we detect that someone is stressed, we send options about what to do with the situation to that person. We don’t send it to the manager so that it can decide over someone’s personal moment.
As Leanmote is API based, the more you connect your apps with the platform, the better information it will collect. This way, Leanmote can be your frictionless and single source of truth.
This principle is about honesty and consent, making sure that the user understands and accepts what type of data we collect.
Users know from day one that we are constantly gathering data and we give them the control of it. They can check their data and choose not to share it on the same platform. Also, we are transparent about why Leanmote collects information.
Leanmote ensures a strong security to all your data. We know that we handle important information that requires the highest levels of protection.
The platform has multiple-factor authentication: password, push notification and Google Authenticator. Also, all data is stored in Amazon Web Services (AWS) which provides safety and strict privacy.
Each user can choose what to show and only the company can see it.
If we talk about ethics, we should talk about intentions. Our intentions are good, Leanmote provides companies with their people data to enhance their working experience. We collect only the data that is useful for this purpose.
What do we mean by enhancing the daily working life of people? To give information so organizations can make intelligent decisions towards their employees. For example, with data we can prevent isolation, burnout, discontent, misunderstandings and more.
It’s all about the context! The holistic point of view that we offer is important to interpret data.
We provide information to analyze the state of human interaction at work. The variety and amount of information that it’s collected let us give accurate data about all users.
We accept feedback because we want to do better every time. If you detect any mistake, please contact us to point it out.
Terms based on these principles
Before you start using the platform, you can see our Privacy Policy and Terms of Service. We have based our terms with these ethics criteria. Check it out!
DORA Metrics, or DevOps Research and Assessment metrics, are like measuring sticks used in software development to see how well teams are doing. They look at how fast software is being made and how often it breaks. These metrics are helpful but don’t always tell the whole story.
Going Beyond DORA Metrics
Do you have your own DORA metrics dashboard? Ok, it’s great at pointing out problems, like if there’s a big slowdown in the work process. But here’s the catch: it doesn’t tell you how to fix the problems it finds. It’s like going to the doctor, finding out what’s wrong, but then having to figure out the cure on your own.
That’s where Leanmote comes in. It doesn’t rely just on DORA metrics tools; it looks at team dynamics to get a clearer picture. It gathers data from tools like GitLab and Jira, where developers work on code and track progress. But it doesn’t stop there. It also looks at everyday tools like Slack and Google Calendar to see how teams are communicating and coordinating their work.
Rethinking Metrics and Context
Productivity can’t be measured solely by developers’ productivity tools and surveys. This may not provide a complete understanding of how developers operate, because it’s not all about the coding, it’s the context in which you are working too. What about the chats? What about the project management tools, the assigned tickets, and the number of events on the calendar?
While productivity tools and surveys offer valuable insights, they should be supplemented with a more comprehensive set of metrics to capture the complexities of work. These could be brainstorming meetings or collaborative moments.
In a recent report from Deloitte’s 2024 Global Human Capital Trends, it is highlighted that there is a need to rethink traditional productivity metrics. This report claims that organizations are getting better at tracking how well people work and what makes them perform better. This is because they can collect, measure, and analyze data much faster than before. They can then use machine learning or human judgment to turn this data into useful advice. For example, they can use a method called organizational network analysis to see how people in a company connect and work together.
The ultimate real metrics you need
To gain a holistic view, we consider three critical areas of measurement:
Performance: go from uncertainty about team efficiency to gaining insight through metrics like story points and time duration, allowing us to prioritize tasks, justify delays, and improve quality by addressing issues like bugs and incidents.
Time efficiency: the lack of structure in meetings and time spent hurts workload and efficiency. By tracking time, Leanmote makes alignment visible and finds ways to improve time management.
Connectivity. Internal Connectivity:Not knowing why someone has low pull request activity is a problem. Tracking their merging time and improving team connections boosts productivity.
External Connectivity: Measuring project complexity by stakeholder involvement. Identifying alignment costs, stakeholder numbers in sprints, and commitment levels make project management smoother.
But, (yes, a “but”), it’s not just about setting metrics. It’s about striking the right balance between different aspects to ensure a sustainable and productive development environment. To these, you have to add the counter-metrics, for example:
Performance vs. Connectivity: Workload. If you have many stakeholders, it will impact your workload as you need to align many things.
Performance vs. Time Efficiency: Working beyond regular hours affects productivity. How many meetings are held per sprint?
Delivery vs. Performance: If I know I need to increase deployment frequency but have a heavy workload and many stakeholders, I need to take that into account. DORA tells you what’s happening today but not why. Leanmote tells you why: if the project is more significant if there are many people involved, and many tickets, etc.
Bring Solutions to Your Team Instead of Problems
With all this, Leanmote provides leaders with a clearer understanding of their team’s dynamics. Instead of relying on guesswork or constantly asking the team what’s wrong, leaders can simply check the Delivery Management feature to pinpoint issues.
Going further, Leanmote provides the Team Diagnostics feature and offers quantifiable insights to understand why objectives aren’t being met. Finally, you have LeanOps which helps leaders to craft action plans and take intelligent decisions to solve the problems that are pushing your team back.
With Leanmote, leaders can confidently make informed decisions, fostering a culture of innovation and collaboration. No more guesswork or blaming; Leanmote empowers leaders to guide their teams to success with reliable and complete data.
Welcome to Leanmote’s Discord integration – a game-changer for evaluating team connectivity. Gain valuable insights into message volumes, group interactions, message timing, and chat statuses, all designed to enhance your team’s communication dynamics. Elevate collaboration with Leanmote’s streamlined approach to team analysis.
What does our Discord integration do?
Leanmote will collect passive data on team interactions, aiding in the evaluation of your team’s connectivity and communication. We collect:
Number of messages between peers
Number of messages between peers in a group
Time/hour of the messages
Chat status
How to start collecting data from your Discord server:
Install our Discord bot on your server by clicking the Discord bot card on Settings – Company’s integrations.
Each user on your team should save their Discord username on Settings – Integrations inside the Discord bot card.
Important: The Discord username is not the same as the display name. You can find your username inside your Discord settings. In this example, the username is “this.is.a.username.2024,” which is the one the user should save on their Integrations tab.
