Loading...
Answers
MenuWhat are the best practices for defining metrics to my tech team?
For marketing we use CAC and others. I am trying to define performance metrics for my tech team - 1 metric to make them user focused, another metric to focus the team on building reliable hardware/software (fewer bugs), and another metric to help them focus on 10x innovative projects. Would appreciate any help here.
Answers
There is not much background information when it comes to what your company is doing, but will try to provide some tips.
Assume you are working with customers and have some kind of ticketing system in place, so for:
1) I would be sending a very short survey with every single ticket just asking customers to rate the service they have received. Extremely well, Very well, Moderately well, Slightly well, Not at all well. This over time will give you very good indications on how the team is doing and how changes you apply impact customer satisfaction. There are many other important metrics when it comes to support but this one is key.
2) Again, no idea on what your product is about but i.e. in our case we monitor plenty of backend metrics. Successful/failed servers, successful/failed applications launched and so on for most important operations on the network.
3) Don't think that there is really a metric for that. You want to measure impact of new stuff you do in already present metrics and correlate success. Letting people innovate is more a culture related thing and how your organization embraces success/failure (as innovating implies failing many times and people will not innovate if they think they job is at stake)
In any case, for any metric to have any impact, it must be OBVIOUS to every one working for you. Make it AS EASY AS POSSIBLE for everyone to check metrics, try to make this a habit for key people in your organization if not everyone. We send a daily heart-bit to everyone with most important metrics and we have a grafana dashboard for each team, accessible to everyone with all historical metrics where people can thoroughly examine trends and see impact of everything we do.
Building a metric based culture, even if difficult is worth every drop of sweat it takes.
Pere
I would give them similar metrics to the ones you give to your marketing folks. If the tech team builds a good, customer-focused product, on time, with few bugs, then the business results will follow. I have seen too much "gaming the system" with milestone or bug-related metrics. If you want to encourage innovation I have found the best practice is, instead of metrics, to give the tech team he space and privilege to do so - e.g., the Google idea to spend 20% of time on whatever they want, quarterly hack days, etc.
I've worked as the Head of Product at my current startup for the past 4 years and have consulted as a product manager to several other startups. Your question leads me to believe that you don't have a dedicated product manager or someone who's job it is to envision, design, and build out your product.
The technology team itself should be measured upon "story points", or points assigned to each task that they are assigned to work on. If you are using the agile software development philosophy, you can measure the story points per sprint to see how much work is getting done. After 2-3 sprints, you should have a really good idea of a) who the most productive members of your team are b) where most of the technology bottlenecks are occurring and c) what skills you have on board and what skill sets you will need to hire for. There are very powerful product management tools that can help you for very little cost.
However, the product management team should be the team that is responsible for envisioning and specifying "user-focused" software and "10X innovative projects". The product manager should be a subject matter expert and should be in contact with clients, prospects, and developers to gather requirements and solicit ideas on how to improve your product. From there, the product manager should create detailed requirements (I personally like agile stories, but there are many ways of doing this) and prioritize each task for the development. The product manager is ultimately responsible for the product, how responsive users are to the product and how innovative and revolutionary it really is in the marketplace.
If you want help setting up your product management team or on additional metrics that you can use to improve your business, I'd be happy to discuss.
I think you are thinking on the right lines. However, as someone who managed tech teams working on products I can tell you it is extremely hard to get these right. You would want to come up with something that you are going to stick to no matter deadlines, sales and marketing pressures, special requests from customers.
Do not get confused between Agile/Scrum best practices with managing people. I have seen teams struggle with estimation and that really leaves the appraiser in a state of confusion on how to judge performance.
Sit down with you team, state your goals - improved customer happiness, reliability and innovation are good enough - and come up with a few metrics, put them in the system for a month or so, review and improve. Do not write this in stone, because each team is different and so is each company.
All the best for a successful product backed by a happy team!
Related Questions
-
VCs: What are some pitch deck pet peeves?
Avoid buzzwords: - every founder thinks their idea is disruptive/revolutionary - every founder says their financial projections are conservative Instead: - explain your validation & customer traction - explain the assumptions underlying your projections Avoid: - focusing extensively on the product/technology rather than on the business - misunderstanding the purpose of financial projections; they exist in a pitch deck to: a) validate the founders understanding of running a business b) provide a sense of magnitude of the opportunity versus the amount of capital requested c) confirm the go-to-market strategy (nothing undermines a pitch faster than financial projections disconnected from the declared go-to-market approach) d) generally discredit you as someone who understands how to build a company; for instance we'll capture 10% of our market, 1% of China, etc. Top down financial projections get big laughs from investors after you leave the room. bonus) don't show 90% profit margins. Ever. Even if you'll actually have them. Ever. Instead: - avoid false precision by rounding all projections to nearest thousands ($000) - include # units / # subscribers / # customers above revenue line; this goes hand-in-hand with building a bottom up revenue model and implicitly reveals assumptions. Investors will determine if you are realistic, conservative, or out of your mind based largely on the customer acquisition numbers and your explanation of how they will be achieved. - highlight your assumptions & milestones on first customers, cash flow break even, and other customer acquisition and expense metrics that are relevant Avoid: - thinking about investor money as your money - approaching the pitch from your mindset (I need money); investors have to be skeptics, so understand their perspective. - bad investors; it's tempting to think that any money is good money. You can't get an investor to leave once they are in without Herculean efforts and costs (and if you're asking for money, you can't afford it). If you're not on the same page with an investor on how to run/grow the business, you'll regret every waking hour. Instead: - it's their money; tell them how you are going to utilize their money to make them more money - you're a founder, a true believer. Your mantra should be "de-risk, de-risk, de-risk". Perception of risk is the #1 reason an investor says no. Many are legitimate, but often enough it's simply a perception that could have been addressed. - beyond the pitch, make the conversation 2-way. Ask questions of the investor (you might learn awesome things or uncover problems) and talk to at least two other founders they invested in more than 6 months ago.JP
-
For every success story in Silicon Valley, how many are there that fail?
It all depends on what one decides to be a definition of a "success story." For some entrepreneurs, it might be getting acqui-hired, for some -- a $10M exit, for some -- a $200M exit, and for others -- an IPO. Based on the numbers I have anecdotally heard in conversations over the last decade or so, VCs fund about 1 in 350 ventures they see, and of all of these funded ventures, only about 1 in 10 become really successful (i.e. have a big exit or a successful IPO.) So you are looking at a 1 in 3500 chance of eventual venture success among all of the companies that try to get VC funding. (To put this number in perspective, US VCs invest in about 3000-3500 companies every year.) In addition, there might be a few others (say, maybe another 1-2 in every 10 companies that get VC investments) that get "decent" exits along the way, and hence could be categorized as somewhat successful depending on, again, how one chooses to define what qualifies as a "success story." Finally, there might also be companies that may never need or get around to seeking VC funding. One can, of course, find holes in the simplifying assumptions I have made here, but it doesn't really matter if that number instead is 1 in 1000 or 1 in 10000. The basic point being made here is just that the odds are heavily stacked against new ventures being successful. But that's also one of the distinguishing characteristics of entrepreneurs -- to go ahead and try to bring their idea to life despite the heavy odds. Sources of some of the numbers: http://www.nvca.org/ http://en.wikipedia.org/wiki/Ven... https://www.pwcmoneytree.com/MTP... http://paulgraham.com/future.html Here are others' calculations of the odds that lead to a similar conclusion: 1.Dear Entrepreneurs: Here's How Bad Your Odds Of Success Are http://www.businessinsider.com/startup-odds-of-success-2013-5 2.Why 99.997% Of Entrepreneurs May Want To Postpone Or Avoid VC -- Even If You Can Get It http://www.forbes.com/sites/dileeprao/2013/07/29/why-99-997-of-entrepreneurs-may-want-to-postpone-or-avoid-vc-even-if-you-can-get-it/MB
-
What are digital products or services you wish existed and why? How would they help you and/or your business?
As the owner of a web development firm, I am always inventing our own digital products and services. Any service that is web-based and accessible to mobile devices work as long as they solve a business need. The digital products I wish would exist are: 1. Home building services including videos by experienced builders 2. Mail and package weighing digital services 3. More security services for document transfer services. BruceBC
-
What is a good/average conversion rate % for an e-commerce (marketplace model) for customers who add to cart through to purchase order.
There is quite a bit of information available online about eCommerce conversions rates. According to a ton of sources, average visitor-to-sale conversion rates vary from 1-3%. This does not mean the Furniture conversions will be the same. The bigger problem is that visitor-to-sale conversions are not a good data point to use to measure or tune your eCommerce business. All business have some unique friction factors that will affect your final conversion rate. It's very important to understand each of these factors and how to overcome them. The best way to measure and optimize is to take a conversion funnel approach. Once you have defined your funnel you can optimize each conversion rate to better the total effect. For example: Top of the funnel: - All web site visitors, 100,000 / month First conversion: View a product page, 50% of all visitors Second Conversion: Add to Cart, 10% of people who view products Final Conversion: Complete Checkout, 80% of people who put items in a cart In this example we see that only 10% of people who actually view products put them in to a cart, but 80% of those people purchase. If you can figure out why visitors are not adding items to their cart and fix the issue to increase the conversion rate, revenue should increase significantly because of the high checkout rate. You can use free tools like Google Analytics to give you a wealth of information about your site visitor and their behavior or there are some great paid tools as well.DM
-
A tech startup fully outsourced. What problems would be in this situation?
The ideal way would be to hire the engineer while the project is still under development. You and the engineer should follow up with the outsourced partner in the process. This will give hold to the engineer and later more staff can be trained in upgrading or follow on versions of the product/service.SM
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.