Team Structures for Speed and Innvoation

 Anand is a VP (Engineering) with a FinTech start-up in Silicon Valley. His firm has built SaaS platform related to payment solutions for retail industry. He has core team of 30 members within his start-up. He has contracted with two technology services firms from India and Eastern Europe to get team of engineers. There are 250+ members working from 5 locations across 4 time-zones. They are responsible for developing and supporting the platform as well as providing professional services to customers. He has created pyramid structure for better control on development and operations. He has also asked technology service partners to provide Single Point of Contact (SPOC) for managing all the interactions.

Sriharsha is a Delivery Head in technology services firm. She manages project delivery of a business unit in the domain on Life Science and Healthcare comprising 3000+ members focused on 25-30 clients in the domain of life science and health care industry. Her business unit is divided into 8 Delivery Units, each managed by a Delivery Partner. She also has specialized teams of Technical Architects, Business Analysts, Program Managers, DevOps engineers, Scrum Masters, etc. as part of her unit. All the teams are organized in the pyramid structure. It helps Sriharsha to engage people, manage operations, drive efficiencies, and scale growth.

David is a Delivery Partner for a Delivery Unit. He manages portfolio focused on 3-4 customer comprising 250-300 team members. He maintains pyramid structure of with ratio of 1:2:5:2 (Project Manager : Team Leads : Engineers : Interns). This pyramid structure enables him to maintain stability and gross margin.

These types of team structure are quite common in the technology services industry. They are helping industry to achieve predictability of growth and profitability. They are also addressing the challenges of employees’ aspirations for promotions every few years and engagement. However, they have also created distance between team-members and customers / end-users. It has reduced focus on innovation to one-off hackathon conducted in a every year.

How might we enable ‘Delivery Leaders’ to solve the conflict of focusing on speed, innovation & customer centricity without loosing the sight of stability, margin and employee engagement?

Answers lies in understanding two principles –

Principle # 10 (SAFe Lean-Agile Principles) – ‘Organize around value’ ^[1]

Principle # 1 (Based on Agile Manifesto) – ‘Our highest priority is to satisfy customer through early and continuous delivery of software’

“The solution is not to trash what we know and start over but instead to reintroduce a second system – one which is familiar to most of the successful entrepreneurs.” – John Kotter (XLR8 – Accelerate : Building A Strategic Agility for a Faster-Moving World). Kotter advocates a dual operating system – A networked organization that is organized around ‘customer journey’ and ‘improves flow of value’ complimenting with the hierarchy structure.

#ScaledAgileFramework provides set of practices based on “Kotter’s Dual Operating System” to create a virtual networked organization within the hierarchy structure to improve speed and innovation. I have found following practices that provides significant benefits –

1.       Move focus from ‘project’ to ‘product’ ^[2]

Technology services organization operates with construct of ‘project’ and within the ‘boundary of SOW (Statement of Work)’. SOWs are created for ‘capacity pool’ or ‘modules / functionality’ or ‘technology service’. It’s essential to align all the team-members working on different ‘projects’ / ‘SOWs’ under an umbrella of ‘product’. Sharing product vision and roadmap, empathy map of the end-users, how product solves the challenges of end-users, economic value of the product, etc. helps team-members to connect with ‘big picture’ of the product. It brings awareness about inter-dependence among team members.

2.       Build ‘development value stream’ for the product ^[3]

SAFe recommends establishing ‘development value stream’ to align all the teams under an umbrella of ‘product’ or ‘solution’. Development value stream converts the ‘feature request’ into an incremental delivery of value thru engineering activities covering define, build, validate and release of product.

3.       Create ‘Agile Release Train (ART) to realize value

Product / Solution can’t be delivered by technical team alone. It requires involvement of business, product management, procurement, recruitment, compliance, security, operations, etc. to deliver working product to end-users. ART provide construct to align all the members across the groups to align. ART operates on set of common principles to deliver the features and flow of value.

4.       Set-up ‘cross-functional’ Agile Teams

Agile team is a fundamental unit of ‘Agile Release Train’. It should be cross-functional team to 6 to 10 members. If team is not agile then none of the aggregating unit can be agile. Agile team should be self-sufficient to perform all the activities from define to deploy. Agile team can be based on value-stream activities, complicated sub-system, integrated technology platform or specialized enabling activities. It’s necessary that all the members across teams have visibility to the features and user-stories that they are working.

5.       Cadence and synchronization

Cadence helps to bring a common rhythm to the teams associated with products even if they are geographically distributed, spread across the organization boundaries and governed by own hierarchy. SAFe suggests leveraging PI planning and roadmap create synchronization and commitment across teams towards customer and business objectives.

In today’s business environment, Delivery Leaders are challenged with balancing ‘customer focus’ and ‘employee engagement’. Industry continues to debate, whether it’s customer first or employee first. Demand-supply gap related to talent availability impacts hierarchical structures and economic decisions. In this environment ‘Organizing Around Value’ enables creation of team structures that promote speed, innovation, customer focus with employee engagement and profitability.

References –

1)      Principle #10 – Organize around value - Scaled Agile Framework

2)      Book - Project to Product: How to Survive and Thrive in the Age of Digital Disruption with the Flow Framework by Mic Kersten

3)      Development Value Streams - Scaled Agile Framework 

Agility as Competitive Advantage

We live in a world that is evolving rapidly. This is evident from pace at which the technology adoption curve is shrinking. In the past, it took decades for a technology to move from research to obsolescence. Today, this cycle has shrunk to years and will soon become months. In this rapidly accelerating world of change, the ability to respond quickly is the key to success.

Agility is the new mantra and is crucial for an organization's survival. Constant demand for newer, faster and better is dictating shorter life-cycles and forcing product manufacturers and service providers to constantly innovate and upgrade. Market uncertainty is further triggered by disruptive technologies, innovative business models and slick execution, creating a new array of unexpected game-changers.

Organizations must learn to adapt and respond with agility in this fast-changing world. An organization must build the culture and the capability to respond with alacrity to customer demands by creating operational flexibility and by empowering individuals.

Agility is the ability to respond with alacrity to changes in market demands, business climates and global scenarios. Organization should embrace agility as a core value to deal with the changing requirements of customers, environments and stakeholders. To be truly agile, we must inculcate agility across all aspects of the Company's culture and ethos. Agility must be all-pervasive and is fundamental to organizational principles, people competencies, process improvement programs and performance measures.

In today's dynamic world, when the life of a product is shrinking, it is important to build and evolve products to meet customer needs. Today's customers are discerning and are sharing feedback through social media. The world has become collaborator where feedback is available instantaneously and sharp reactions can make or break a product. Agile product development has become an accepted practice for building products. Agile development techniques are based on iterative and incremental development techniques, where products are built with short cycles, encouraging rapid and flexible response to change. Organization need to adopted design thinking and iterative development approach for effective execution.

Another key component of organizational agility is development of people competencies, which covers behavioral as well as technical competencies. The former include being pro-active and connecting with the big picture, while the latter include techniques such as lean Six Sigma methodology, theory of constraint philosophy & associated methodologies, techniques for waste elimination, Kanban and change management.

While embracing agility, organization should also look at its performance management system. Throughput improvement, cycle-time optimization, system effectiveness, etc. are true measures for agility.  

Agility is one of the rare ability of the organization which can create direct impact on organization as well as on its customers. It can help all the entities to grow together. It even helps the end-users for faster realization of value. In true sense, it can create win-win situation for all the stakeholders. Given all the benefits and investment parameter constant, it can help organization to create disproportionate advantage by delighting its customers.

What is your 'Mission Quality'?!...

Having clarity of mission & vision is pertinent not only for the organization but also for ‘Quality function’ within the organization. In my humble opinion, it provides an individual all the answers to live & work.

About 8 months back, I have taken new role to lead Quality function for my current organization. We are a medium size IT enterprise providing services for product engineering, platform integration and digital transformation. During my first 90 days, I continuously asked this question to myself, my team members and key stakeholders i.e. if we close-down ‘Quality function’ today, what will the ‘organization’ miss?

I found following answers -
1. We help organization to mitigate risks and solve today’s problems those are creating hindrance to delivery value to customer.
2. We enable organization to scale by developing process and technology capability.
3. We support organization to adapt to the changing environment and be relevant.

In other words - "Create Capable and Sustainable Organization" has become our mission. This keeps us going. It motivates me to come to work everyday. This mission and associated vision guides me in never ending journey to create & contribute, add value and attain results, learn & grow, play & be happy.

5 Lessons from David & Goliath

'David and Goliath' story teaches victory doesn’t always belong to giants, powerful or brilliants. In the battlefield of life or business even small, ordinary or underdogs can win by being persistent, following instincts, leveraging strength and targeting competitors’ weakness.

These parable offers following learning for small and medium businesses (SMBs) in IT services industry. These learning are applicable to any IT service organization, because even the large organizations might be small or medium in certain market segment.

Lesson # 1 - Create own rules for execution based on strength and aligned with parameters of differentiation

Majority of the service providers focus on budget, schedule, best quality and fulfill value promise while delivering service. These are essential elements of predictable service delivery. Predictable service delivery helps service provider to manage its own operations efficiently. One tend to pad the execution with extra resources for smooth delivery & de-risk the execution to avoid any surprises.

SMBs should change the execution focus to best time-to-market, optimal business value and acceptable quality. Focusing on cycle-time and optimal value will force to be customer centric and prioritize customer requirements. They should embrace iterative and agile development across most of the engagements. They should negotiate with customer for broader scope, high level acceptance criteria and evolving requirements. ‘Cycle-time and business value’ are the only measurements that create win-win situation for customer & service provider. However this will be feasible when they deliver hygiene and tolerable quality.

Lesson # 2 - Strike the balance while making investment - relationship between outcome and resources is ‘inverted U’

It is feasible to explain most of result – resources relationship in form of Y = f (X). One tend to believe that as the investments and resources increase the result or outcome improves. Initially result improves directly in proportion of resources deployed however after certain threshold value rate of improvement starts diminishing. This was well proven and explained by economists thru law of marginal diminishing returns. Though this is not entirely true for increasing investments. After another threshold value, the returns starts reducing even if one tends to invest more.

SMBs need to find optimal team size that can be managed to deliver the projects in agile manner. Team size of 9-14 resources is optimal to run the engagements agile way. One may design infrastructure to facilitate close interactions with customer and within team. In case of large program one can take approach of running iterations at portfolio, programs and projects.

Lesson # 3 - Be the big player in niche market rather than average player in large market

Traditionally large markets are lucrative. Rules of engagements are well known. They are easy to penetrate. There is a room for everyone. Majority of SIs are targeting Fortune 500 and Global 1000. They are after big government contracts. These customer offers steady stream of business that supports the need of scale.

US mid-market (10 – 1000 mUS$) has 200K + organizations. Out of these 2000+ are in 500-1000 mUS$ range. US mid-market GDP is 5^th largest economy after US, China, India and Japan. Even among the EU-4 (UK, France, Italy, Germany) growth of mid-market is more than big markets.

Mid-markets are planning 12% investment in IT. Their primary challenges are to reduce employee healthcare cost and improve margin. SMBs should aim to build relationship partnership with mid-markets rather than being a fringe play for large corporations.

Lesson # 4 - Tough times are necessary to shape character

In modern day literature has advocated this enough and more. There are many quotes – ‘tough times don’t last, tough people do’, ‘the difference between stumbling blocks and stepping stone is how you use them’,  ‘what lies behind you and what lies in front of you, is pale in comparison with what lies within you’, etc. indicate that adverse times are essential to push one’s limits.

Number of big IT organizations rapidly grew during 2002 to 2008. Significant numbers of current lot of new managers have joined our industry during that period. They didn’t see adverse times till we hit the financial crisis of 2008. Majority of them struggled to cope with lack of growth, adoption of new services, no salary hike, inadequate resources, etc. They haven’t yet come to terms with single digit salary hike even after 5 years of crisis.

SMBs were small and struggling for resources during that period. They have learnt it hard-way about what it takes to innovate, be agile and develop technology prowess. These aspects are ingrained in their middle-managers. They should leverage these competencies. They should empower and challenge middle managers to take ownership. Managers should open the dialogue with customers, focusing on innovation and operational excellence. It’s a time to leverage openness, conscientiousness and disagreeableness to take bold risks. As George Bernard Shaw once put it: “The reasonable man adapts himself to the world: the unreasonable one persists in trying to adapt the world to himself”

Lesson # 5 - Not all the wars of worlds are won by sheer use of power

Being # 1 or 2 in industry or market segment, having hundred-thousands of work-force, multiple billions of market capital, etc. provide comfort of being powerful, rich, wealthy and strong. It gives assurance that we can throw resources at any problem and it can be conquered. Though it is not a guarantee of success.

Being small, nimble, resource starved position has perception of lack of power. Player with these attributes need to operate by leveraging innovation, excellence, conviction in one’s ability, hard-work, talent and persistence. One need to commit to discipline, rigor and contribution.

Battles of life aren't always won by powerful, fastest, strongest, wealthy and mighty... Most of the time victory belongs to courageous and the one who believes he can.

PS – This is written based on ‘David & Goliath: Underdogs, Misfits and Art of Battling giants’ by Malcom Gladwell. I have made a modest attempt to adopt the core concepts explained in book for SMBs in IT services industry.

Beyond Traditional Quality…

This is a quite pertinent question to ask. As we are celebrating 25th anniversary of quite a few models, standards and philosophies those have shaped modern day Quality profession and professionals, it is necessary for us to look at history and learn from our evolution.

Initiation of Quality profession can be traced to ‘guilds’ in 13th century. Those were the days of individual craftsman and individual’s competence played significant role in determining Quality. During industrial revolution period, the relationship between quality, productivity and cost was established. Impact of Quality was observed not only on customer experience but also on operational performance. The early 20th century has taken quality from localized improvements to across the value chain thru ‘process’. In the post world war II era, Quality Gurus’ have shared multiple philosophies and principles. Majority of them were focusing on role of leaders and management in promoting Quality and continuous improvement in the processes in order to improve Quality and operational performance.

1987 is a tipping point for Quality. During that year, we saw emergence of multiple models and standards like MBNQA for business excellence, ISO 9000 series as standards for Quality Management Systems, Six Sigma improvement paradigm at Motorola and Process Capability Maturity Model at Carnegie Mellon University.

Based on this historical perspective, I observe 5 phases in the Quality evolution.

1. Quality as individual’s competence
2. Quality control
3. Quality assurance
4. Quality to improve business performance through process management
5. Quality for business excellence and sustainability

Though, it is difficult for me to say which phase should be termed as traditional quality.

It is essential for Quality professionals to bring all the stakeholders of Quality profession on common ground. If leader’s vision for Quality, management’s commitment to Quality, expectations of organization stakeholders from Quality and competence of Quality professionals are not aligned, that it may lead to confusion and chaos in the operations. In my understanding, Organization needs to go through all the phases of evolution till it reaches to 5th phase. 5th phase is a journey that should become integral part of culture / DNA of the organization.

Stakeholders’ expectations may vary from Quality function based on their immediate need, understanding and exposure to different phases of Quality evolution and perception of Quality professional’s competence. Quality professionals need to identify the appropriate phase for the organization based on industry maturity, competitive land-scape and leader’s vision for organization. They should understand the different competencies required for each of these five phases and invest into self-development. Quality professionals are change agents. They help organization eco-system to transition from one phase of quality to another. This transition brings prosperity and development for organization, its stakeholders and society at large.

Salute to my teachers...

ज्ञानशक्तिसमारूढः तत्त्वमालाविभूषितः ।
भुक्तिमुक्तिप्रदाता च तस्मै श्रीगुरवे नमः ॥

O Guru I salute you for sharing power of knowledge influenced by the principles and blessing me with prosperity and freedom.

Mentor is the person who –

-  Allows Me to be who I am
-  Energize towards purpose
-  Nurtures strengths
-  Tests commitment
-  Expands hOrizon
-  Focus on getting Result

In the network economy every interaction is a learning opportunity thus mentoring is "live the moment and learn from it".

Emerging Role of Quality Professionals...

Year 1987 is a significantly important date in the history of Quality. This is the year where multiple quality systems standards and business excellence model were published across the globe. ISO 9000 / Software CMM moved the Quality from discrete / transaction oriented to continuous / process driven. There were lots of approaches defined and developed prior to this era, but these approaches are easier to understand, adopt and deploy. It has also laid the foundation for process excellence. As we understand, today’s Quality position is –

• Customer defines requirements
• Quality is all about satisfying customer’s stated and implied requirements consistently
• Quality also defines the economically viable approach to meet those requirements

If one looks in macro terms, customer and service provider are both part of the one single eco system, which is governed by the industrial & economic environment. Based on bargaining power of different entities in the environment, organization needs to continuously evolve it self. Role of Quality is to ensure that organization remains focused on its purpose and continuously reinvents itself to meet the demands of eco-system. Given this context role of quality professional merely for monitoring and control is completely inadequate. In traditional ways role of quality was equated as “police-man” or “referee in a foot-ball game”. To put it into right perspective role of quality is like a “coach” not as “umpire” in a cricket match. The visible part of “coach” role is about providing guidance, but its just one part of story. Here is an attempt to describe changing role of quality with the example of the coach.

• Coach is “involved” in the game and takes “bottom-line” for results
• Coach needs to continuously assess the progress towards goals and provide feedback to the team
• Coach’s need to focus on multiple stakeholders’ objectives – right from "play for country’s pride" and team’s success.
• Coach may raise issues against the captain, if he is not focused on team’s success
• Even the best-in-class players require coach’s guidance & support

Though we can relate with these aspects from Quality Team in current context, there are also few more behavioural traits that Quality Professional need to develop i.e. Being proactive, Commitment, Continuous learning, Humility, Integrity, Team-work. Quality is all about “Enabling Excellence through Partnership”, and being PARTNER mean “Perseverance, Actions, Reaching-out, Team-work & Nurturing for Excellence & Results”