What are Vanity Metrics?
What are Real Metrics?
You can contact me @ kkanakas on twitter with your comments
You can contact me @ kkanakas on twitter with your comments
|
Our solution costs
|
Bakery Savings
|
||
|
Solution Cost
|
$100,000
|
Revenue/Bakery
|
$600,000
|
|
Maintenance Cost
|
$20,000
|
Gross Profit @ 2%
|
$12,000
|
|
Integration Cost
|
$150,000
|
Branches
|
100
|
|
Total Solution Cost
|
$270,000
|
Gross Revenue
|
$60,000,000
|
|
|
|||
|
Indirect costs
|
|
|
|
|
One Headcount
|
$150,000
|
|
|
|
Training all bakery staff
|
$100,000
|
|
|
|
Total ongoing costs
|
$250,000
|
|
|
|
Total Cost
|
$520,000
|
Savings per year
|
1,200,000
|
|
Total Payback
|
Within 5 months
|
|
|
| Jobs to be done | Old Solution | New Solution |
| Provide financial services to communities with little income |
Get people to put assets as collateral and charge high interest | Provide the ability for the entire community of villagers to get smaller amounts of money that they can start a business or have the ability to payback |
The case I am trying to make is that innovating is not just the realm of the hip and the cool but it is also about practical utility. Anything that is practical and designed in a empathetic way has a higher chance of success than something that is hip and cool and introduced way to early in the market space. I think in the current day and age where technology is improving by leaps and bounds we are losing sight of simple things that can drive innovation.
I would encourage you to try it out yourself and let us have conversation. I can tell you based on my personal experience it has helped me to convey some of the complicated things in life in simple terms.
As always appreciate your feedback via Linkedin, Twitter, or you post your comments in the comments section of this blog.
The bottom line is empathetic design keeps the user in mind and whether you use cases in development or any other methodology in any other department it will be doomed to failure if all departments fail to have the same understanding of the problem the company is going to solve for the user.
(BTW All the companies I mentioned here are just to make a case, I am not endorsing that my experience is commonly shared, but if you look at their 10K, it proves my point. Your experiences may vary)
You can contact me @ kkanakas on twitter with your comments
Yes, I am little over analytical on matters such as that and sometimes the window opportunity goes away. But there are also times where I don’t think much and just do it, those moments sometimes payoff but most of the time I end up saying maybe I should have gone slow. In my line of work I get to see a lot of complexity in how we build software and there are a lot of moments where we over think a problem, make the problem more problematic than it already is. After going through several discussions around this topic with folks that much more smarter than me I have narrowed them down to 3 things:
1- Product must be simple
This to me is the golden rule. When you make your end user or client think for just the basic functions you have lost them. The immediate gut reaction is “If the basic function is so complicated, I wonder how the complicated functions are”. And once that mindset takes hold it is a uphill task to regain any lost ground. I am not saying that you make your product idiot proof, because that would be wrong and painting everyone with the same broad brush. There can be features that require some advance thinking but those things are not features that everyone uses everyday i.e. the HotSpot feature on Smart phones, how many people truly know how to use that?
2- Product must understandable
To this day I have not figured out what was the purpose of the scroll lock key on a keyboard and why is it so important to keep the key on a standard keyboard in the first place? When you don’t make products understandable for basic functions, it makes the end user feel like the product is talking down to them and somehow questioning their intelligence. Don’t do that, you might start alienating people without even knowing it.
3- Product must be complete
Last point is when you think of the basic function or whatever basic scenario you are delivering. Make it complete. A great example of a complete product is a power utility company, when you have electricity the only thing you worry about is flicking the switch and the power comes on. You don’t even think about how the power gets transmitted to your home. That is a complete product and definitely miss it when it not there because it has become such an integral part of your life
These are just some of my musing on how a product or service ought be delivered. There are several great examples of these ideas in the market place today. Just think of them if these products did not have these capabilities would you have incorporated them into your daily lives.
So what is a tactic ? Tactic could either product, promotion, or service it is the execution arm of strategy and tactic (product/service) can continue to change at a greater pace than strategy. Strategy is turn is built upon a vision and hence strategy can change because it all about capturing value but maybe not at the same rate as a product (strategy is not about increasing sales. If you provide value the sales will follow). Vision of a company usually takes longer to change.
Most of my friends know that I am an Apple fanboy and it is not just because I am addicted to their products but Apple is one of the few companies that illustrates these points well (BTW I am not being paid by Apple to write this blog, I just love what they do).
Apple’s Vision: Enrich peoples lives with their products
Apple’s Strategy: The best integrated experience of software, hardware, and services
Apple’s Products: I think we all know these really well
Other companies that exhibit these traits are Amazon, Johnson & Johnson, Brembo, Lincoln Electric, P&G etc. There are a lot a good companies that understand such distinction.
Maybe next time when I hear someone talk about coupons as a strategy, I might be able to collect my thoughts better and explain the difference.
(BTW I am not claiming that I am in expert in strategy or that I know enough about strategy. Like the blog says these are just my musings. If you find something else that has better explanation of strategy please let me know)
You can contact me @ kkanakas on twitter with your comments