Blog

  • Digital Tranformation Talent – Four key areas

    From HBR: Digital Transformation Comes Down to Talent in 4 Key Areas

    The four key areas should be no surprise to many, but I believe business strategy talent is missing. Digital Transformation has to start with business strategy.

    More than anything else, digital transformation requires talent. Indeed, assembling the right team of technology, data, and process people who can work together — with a strong leader who can bring about change — may be the single most important step that a company contemplating digital transformation can take. Of course, even the best talent does not guarantee success. But a lack of it almost guarantees failure.

  • Successful startup team composition

    From HBR: What Makes a Successful Startup Team

    The focus of the article is on startups, but the same lessons apply to enterprises as well. The successful teams have both hard (past experience etc.) and soft skills (passion, common goals etc.). The soft skills manifests in enterprises as alignment amongst various teams/levels and passion for common product goals.

    What makes a successful startup team?

    One common answer is that prior startup experience, product knowledge, and industry skills predict the success of a new venture. But is prior experience sufficient for a team to work well together? In a recent study of 95 new startup teams in the Netherlands, we explored that question.

    We found that experience alone was not enough to make a team thrive. While experience broadens the teams’ resource pool, helps people identify opportunities, and is positively related to team effectiveness, a team also needs soft skills to truly thrive. Specifically, our study shows that shared entrepreneurial passion and shared strategic vision are required to get to superior team performance as rated by the external venture capital investors.

  • Cloud battle over low-code and no-code

    From CNBC: Next frontier in Microsoft, Google, Amazon cloud battle is over a world without code

    A must-read for anyone in technology. I believe low-code/no-code will be one of the top disruptors in the upcoming decade. Low-code will disrupt software development similar to the way cloud disrupted (and continues to disrupt) infrastructure.

    Google Cloud recently acquired AppSheet, one of the biggest players in the “low code” and “no code” software market, which allows business people to develop apps without specialized coding skills.

    A Microsoft executive tells CNBC it expects low-code, including its Power platform, to be a major source of revenue, and the market has swirled with rumors about an ‘Amazon for Everyone’ product from AWS.

  • How Asia’s richest man is trying to build the next global tech giant

    From CNN: How Asia’s richest man is trying to build the next global tech giant

    Mukesh Ambani wants to build the next global technology company. And if he plays his cards right, his mobile carrier and technology juggernaut Jio Platforms could soon hold rank alongside the likes of Google (GOOGL), Amazon (AMZN), Alibaba (BABA) and Tencent (TCEHY).

    Jio Platforms already has an ecosystem of apps —which feature everything from online grocery shopping to video streaming — that it serves to the 388 million peoplesubscribed through the Reliance Jio mobile network in India.

    Now, Asia’s richest man is getting even more ambitious. In the span of a few weeks, he’s amassed a $9 billion war chest from Facebook (FB) and a clutch of A-list American investors to fuel the next phase of his domination of India’s internet, the fastest growing in the world.

    Ambani “definitely [wants Jio Platforms] to be more than just a telecom company. They want to be the next Google or Tencent of India,” said Wylie Fernyhough, an analyst with PitchBook.

  • Era of SaaS Decacorns

    Thanks to SaaStr for a great read and list of SaaS Decacorns. Key takeaway:

    According to Gartner, while IT is undergoing one of its most massive contractions of all times … -8% (!) in 2020 … Cloud and SaaS are still growing. Cloud is still projected to grow +19% in 2020, and SaaS 20%+. That’s during a -8% contraction in IT spend..

    Here is the list of the SaaS Decacorns as of May 2020:

    No alt text provided for this image
  • Conquering Analysis Paralysis

    Have you been part of teams where after weeks or months there is no progress because things keep getting stuck in analysis? If any of the following examples sound familiar to you, then you have witnessed analysis paralysis (also known as paralysis by analysis) for sure:

    1. Development team had to finalize selection of a tool in 3 months, but the pros and cos are still being analyzed and the final tool is yet to be selected.
    2. Business Analysis (BA) team has captured 99% of the requirements in a month, but getting to the elusive and perfect 100% is now taking months
    3. Data team had to scrub the data to be loaded into the new system, but the rules and their merits are being “validated” when the go-live is round the corner
    4. A research team should have completed the research and produced a concrete recommendation in a month, but it is still collecting data after a couple of months

    Why does analysis paralysis happen?

    Most teams realize that analysis paralysis can cause major delays and make their teams lose credibility. But then, why does it continue to happen and why do teams let that happen? I believe it usually happens due to one or more of the following:

    1. Team is trying to gain consensus from ALL involved, though some disagree and have differing viewpoints or objectives. A variant of this is when the team wants to make sure NOTHING is missed i.e. the pursuit of the elusive perfection.
    2. Team is (a) afraid to make decisions or (b) doesn’t know how to make decisions or (c) is waiting for someone else (higher ups?) to make the decisions.
    3. Team is unable to influence, nudge or negotiate to the common outcome desired, especially with various personality types (analytical, emotional driven etc.) involved.
    4. Team kicks the can as much as possible as there are no consequences or incentives to make timely decisions.

    How to conquer analysis paralysis?

    How do we conquer analysis paralysis then? A good part of the solution comes from changing individual behaviors or team culture. You can conquer analysis paralysis at an individual and team level by following these guidelines:

    1. Action! The best antidote to analysis paralysis is taking action. But, be careful to work within permissible confines of your organizational culture or things may backfire.
    2. Adopt a work approach that has decision making embedded or forced. For e.g. the following common approach in consulting – defining problem statement, proposing 3-4 options, evaluating the pros and cons and then providing a recommendation.
    3. Don’t aim for perfection – Realize that there is NO perfect product or technology. Perfect quality is a myth and definitely not attainable in a given timeline. Don’t get caught up in continuous improvement to get to perfection.
    4. Use resources, time or money pressure in your favor. When groups are up against time, resources and money, it forces groups to make decisions or act. Reiterate how lack of decisions negatively impact the outcome. For e.g. loss of customers, product delays.

    If you are facing “analysis paralysis” in any of your endeavors, you have to acknowledge and address it. It saps energy, wastes time, reduces morale, and usually benefits no one – not even the procrastinators.

  • 10 Rules, Quotes, or Laws of Meetings!

    I am sure you’d have read many books, articles and blogs on meeting facilitation and management and you’re all experts on this topic. Yours truly has concocted 10 quotes/rules/laws on meetings drawing “inspiration” from various sources – science, literature and even divine. I need your help to distill this down to the ones that really resonate with you. Please list the ones that you like the most and the ones you dislike. Also, feel free to comment or add new ones – I know we need a more positive quotes. Without further ado, here are the 10 rules/quotes/laws of meetings:

    #1 It is good to have a meeting with a good facilitator. It is better to have a meeting with prepared participants. It is best not to have the meeting in the first place!

    #2 Ignore participants who shout or speak a long time in meetings and you won’t miss much.

    #3 Why bother attending a meeting, when someone didn’t bother with an agenda?

    #4 I came across a fork, I declined the meeting and that made all the difference.

    #5 Meeting that starts on time is likely to end on time. Meeting that doesn’t start on time is not likely to end on time. It is that simple, folks!

    #6 Meeting’s success can be measured by its actual duration – the shorter the better.

    #7 I went around looking for the bad in other’s meetings, only to realize mine were the worst.

    #8 More the mass in the meeting room, less the velocity of the meeting.

    #9 What is the purpose in attending a meeting, if the meeting doesn’t have a purpose?

    #10 The only time meetings are fun, it is called Sports.

  • A primer on projects/services contracts

    One of the key decisions a customer will make during the start of a project or product is the type of contract to negotiate with the consulting partner, assuming there is a need for a partner. Before we get to popular contract arrangements, let us differentiate fixed vs. variable costs and scope. These are factors that you should consider to finalize the contract type:

    • Fixed and Variable Cost – Cost can be fixed or variable. To use a simplistic example, a fixed price menu is fixed cost and an a la carte menu is a variable cost.
    • Fixed and Variable Scope – Scope can also be fixed or variable. In fixed scope, scope is clearly defined with clear boundaries and requirements and in variable scope, there is room for scope change through the course of the project.

    With this understanding, let us look at the three most popular contract or Statement of Works (SOWs):

    • Time & Material (T&M)
    • Fixed Bid
    • T&M with Cap (also called Not To Exceed)

    There are other types of contracts (for e.g. outcome/results based – risk/reward, value or profit based), but a majority of service contracts fall in the above three categories. Let us go into the three common pricing models in detail.

    Time & Material

    Time & Material is an input based pricing model. Time & Material is in many cases the preferred vehicle of consulting partners. Simply put, it is the number of hours charged at a given billing rate for the various people working on the project. For e.g. if a partner is called to do a simple CRM “out of the box” implementation estimated at 500 hours and the billing rate is $200 per hour.

    • T&M Professional Fees = Number of hours x Billing rate
    • Professional fees for the specialist = 500 hours x $200 per hour = $100,000

    There maybe other expenses involved (for e.g. travel), but the above example covers the key labor considerations. 

    Fixed Bid

    Fixed fee is an output or results based pricing model where a fixed fee for the entire project is agreed upon irrespective of the actual hours spent by the consulting partner. Fixed bid projects have increased over the past decade as customers (i) look to adhere to the agreed upon the budget or strategy plan and (ii) want the consulting partner to take the project delivery risk and have skin in the game.

    Let us say the same customer signs up a consulting partner to do the above said CRM implementation for $120,000. The partner has done tens of such engagements, is very good at it and knows the ins and outs of it:

    • Fixed Fee = $120,000 for professional fees

    Usually, the fee is broken into milestones or stages. For e.g.

    • Milestone 1 – Requirements and Design completed – $30,000
    • Milestone 2 – Configuration and development completed – $40,000
    • Milestone 3 – Testing and deployment completed – $50,000

    T&M with Cap

    Time & Materials (T&M) with Cap can be thought of as a hybrid between T&M and fixed fee. The customer pays the consulting partner on a billing rate basis, BUT (and it is a big but) with a Cap i.e. the partner cannot charge more than the cap. In the T&M example, we said:

    • Fees for the consulting partner = 500 hours x $200 per hour = $100,000

    If the customer signs up a consulting partner to do the CRM implementation with a T&M Cap of $100K, the partner CANNOT exceed the $100K limit i.e. $100K becomes the Cap.

    In summary, we introduced three common pricing models with simple examples. There is a lot more to contracts than these simple examples, but I hope these differentiate the three major available contract vehicles.

  • Four takeaways from “2015 Internet Trends”

    Mary Meeker and KPCB’s Internet Trends is probably the definitive source on the latest Internet Trends. It has been published for 20 years. I’ve found that it also serves as a treasure trove of information on technology and economic trends – two areas I enjoy and follow.

    I checked out the 2015 report very recently and was I surprised? The report covered a wide range and were fascinating:

    • Key Internet trends
    • Re-imagining the way people use technology
    • Big Internet markets
    • Evolving US work environments
    • Private/public company data

    My four takeaways are summarized below. I should admit that the first one stunned me and the other three surprised me:

    1) China and India as % of Global GDP

    • China was 33% of global GDP in 1820 and 16% in 2014
    • India was 16% of global GDP in 1820 and 7% in 2014
    • US was 2% of global GDP in 1820 and 16% in 2014
    • Europe was 27% of global GDP in 1820 and 17% in 2014

    Maybe I didn’t pay much attention during my MBA economics class, but the % of GDP numbers for China and India were an eye-opener. The #s put in perspective the claims of some that China and India have yet to regain their “lost economic glory”. After all, it may not just be a matter of pride. In a few decades will China reach at least 25% and Indian reach at least 12% of global GDP? Refer slide 95 of the report for further details.

    2) Innovations in the Enterprise space 

    Innovation in the Enterprise technology space was particularly illuminating, where the Entrepreneurs “often pursue prior company pain points”. I haven’t even heard about some of the companies and I believe are worth checking. Here is the list of companies listed. Refer slides starting 30 for further details.

    • Slack
    • Stripe
    • Intercom
    • Gainsight
    • Directly
    • Zenefits
    • Anaplan
    • Greenhouse
    • Checkr
    • GuideSpark
    • Envoy
    • Square
    • Domo
    • DocuSign

    3) Freelancers as % of US workforce

    More people than ever are working in flexible/supplemental jobs in the USA. Freelancers are the significant and growing part of the overall US workforce @ 34% i.e. more than one-third of the entire workforce. Refer slides starting 125. 

    4) Mobile viewing as % across all platforms

    Mobile viewing is 29% vs. 5% just five years ago in US. We spend close to one-third of our overall time viewing on mobile screens compared to all (including TVs, laptops, desktops) platforms. Refer slides starting 24.

  • Six design principles for SaaS projects

    Many of us are aware of the benefits of following design principles in projects. Design principles:
    1) Provide guidelines to design solutions
    2) Help with consensus building
    3) Speed decision making

    For e.g. when stakeholders have differing views, running against the design principles helps the team narrow the design options and choose the recommended solution.

    Here are the six design principles for a strategic SaaS project I am leading. A couple of principles are customized to the project, but many are generic and can be applied to any SaaS project.

    1) Requirements or design should clearly demonstrate value i.e. usefulness to users
    2) Follow industry best practices – Many have walked through this path before, there is no need to “reinvent the wheel” unless it is a competitive differentiator
    3) Differentiate between business “need” and “want” and prioritize
    4) Keep it simple – Solution should be simple for users to adopt and these are usually the best solutions
    5) Leverage platform capabilities “out of the box” – Avoid customization unless it is to implement best practices; this helps to keep the solution simple and standard
    6) Don’t aim for perfection – Don’t let perfection be the enemy of good as it isn’t attainable