I'm Kshitij, CEO of typo - an engineering management platform. Ask me anything!

Hey @anirudh_joshi1, appreciate your support. The current live integrations are : - Git Providers : Github, Gitlab, Bitbucket - Issue Trackers : JIRA - CI/CD : Github Actions - Chat : Slack We're coming soon with a lot more like Jenkins, Linear, ClickUp, SonarQube, Google Calendar etc. Will keep you posted with the launch updates. Cheers!

Hi @breakthemyths, thanks for the question. I'm glad you liked the product. We understand there are similar products trying to solve the problem but the biggest difference is in the approach. Just presenting with some metrics & data points is not the real solution - the idea is to build a holistic approach by co-relating performance, collaboration & wellbeing together to maximise productivity. That's how we are trying to create the difference - presenting with right visibility & insights and then giving action items to drive improvement. Hope this answers. Cheers!

@kshitij_mohan make sense I’ll surely refer this to my development team

Hi @nitesh_chandel61, thanks for your question. Since there is no straight-forward way to measure it, we do it holistically by two ways - active & passive. 1. We identify unhealthy work patterns & start flagging if a developer is continuously over-loaded with work 2. We trigger Pulse Check-ins based on developer experience framework that collects anonymous feedback on monthly basis & highlights wellbeing levels across teams. Hope this answers your query. Happy to know your thoughts on the same. Cheers! 👍🏻

Thanks @satish_kumar23 for asking this super relevant question. As a tech lead, there are two main things that you would be focusing at : ensuring timely delivery & increasing your team's efficiency. That's exactly where typo helps EMs. You get to see real-time metrics of Velocity, Quality & Throughput for your team to identify inefficiencies & bottlenecks that can cause delays in delivery. Secondly, we help you build improvement goals to ensure your team follows best tech practices to ensure right hygiene. On top of that, you get to understand your team's wellbeing levels to work on high-impact areas. Hope this helps. Please feel free to sign up for typo for free & see the magic in action! 🚀

Hey @satish_kumar23, thanks for the question. I would say the learning never stops. Every single day - it feels we are learning something or the other. The perspective keeps changing, you get to deep-dive into new challenges every day, moulds you for better. The most important thing - solve only that problem which you are deeply passionate about. Coz when the going gets tough, it's only your belief that helps you sail through. Keep building. Cheers! 🚀

@jagrati_gupta glad to know that you liked our name 😁. It's a satirical take on what we are trying to solve - removing errors & inefficiencies in the tech ecosystem. 🚀

Hey @madhurima_sabharwal1, thanks for the question. While being a part of software organisations over the past 10 years, I have closely worked & seen how engineering teams function. Amid the constant chaos of shipping code fast, there has always been a bias or lack of real-time data to support better decision-making. That's how typo was born - to support modern software teams with real-time visibility, insights & tools to maximise dev teams' performance. Looking forward to your support on the launch day. Hope this helps. Cheers!

Hey @narenbhandary, thanks for the question. Inception to launch has been an interesting journey spread across multiple phases - Idea --> User Interviews --> Feature Roadmapping --> UI/UX --> User Feedback --> Development --> Alpha --> Beta --> Final Launch! 😅 This entire process took us almost an year as we wanted to be very sure of what we were going out with the first product offerings. We didn't use any no-code tools for the development, however we use a plethora of tools for other purposes - Notion, Tidio, Zeplin, Airtable, Dripify, Apollo & a lot more to streamline our processes. The golden rule that I personally follow - don't build something that's not your business focus. Get as many tools as possible to execute fast as that's what matters at early stage! Hope this answers. Cheers! 😁

@kshitij_mohan Great answer Kshitij. Cheers!

Hey @roshanraghavander, thanks for reaching out. Delighted to hear that you would like to work with us. However, I am really sorry we do not have any open positions for now. Will surely keep you posted if any opening comes up. Would be really helpful if you could spread a word about us. Cheers! 👍🏻

Hey @nerd_aryan, that's an interesting question. We talked to 100+ Engineering leaders of high-growth organisations & created a need-map on what matters most to these individuals. Then, we presented them with a view that tried to capture their problem statements. After multiple iterations, we have reached to where you see the product today - all metrics co-relating to each other in a way that makes most sense. Having said that, no engineering teams have same requirements. Hence, we have kept them configurable & customise as per the organisation needs. Do try out our product as well & see if you can share some feedback to help us improve. Cheers! 👍🏻

Thanks @ashok_kumar_singh2 for the question. I am glad you tried out our product & found real-value. Finding the right balance between work type is one of the major challenges that every Engineering leader faces & that's why we have a feature called Investment Distribution - this helps you auto-track your team's efforts spent across tech debt, innovation, bugs & more. And, the best part - you can customise these categories as per your requirements. Hope this answers your question. Please feel to try it out & ping me if you are stuck somewhere. Cheers! 👍🏻

Hi @neha_khan78, thanks for your question. In brief, Typo is an intelligent Engineering Management platform that helps modern software teams with the right visibility, insights & tools to drive maximum efficiency. Hope this helps. Cheers!

Thanks @neha_khan78. Would need your support on the launch day, that's tomorrow. :)

Hey Naveen, thanks for the question. I have always been following one approach - prioritise as per your users needs. We create a list of identified requirements & then do customer interviews. Based on these discussions, we create a final priority list of product roadmap & user personas accordingly. You can't always be 100% sure but this approach has always helped us take an objective path.