Sunday, May 17, 2026

5 Step Process to Facilitate Negotiation Among Multiple Stakeholders

 

(Reference - CHATGPT generated on 17MAY26 with ref - c0f12eab-e4c0-47d7-bfbf-9ccd72452b0e)

In this blog-post, an attempt is made to present a negotiation-cycle comprising of following steps: -

Initial State à Negotiation à Agreement à Execution à Final State

The negotiation step in this negotiation cycle is further represented through following 5 step negotiation process: -

Clarity à Trust à Risks à Conflicts à Convergence

The purpose is to present a possible process to negotiators dealing multiple stakeholders.  

(1)   

The Negotiation Cycle

Negotiation happens in many areas of life, such as business deals, workplace discussions, conflict resolution, and even everyday situations like deciding plans with friends. But, what exactly negotiation means?

“Negotiation is the process by which parties bargain in an effort to reach an agreement. Parties often negotiate the terms of a contract before entering into it.” (Ref – Cornell Law School)

We will assume that a negotiation is a structured process of communication and bargaining between two or more parties intended to reach a mutually acceptable commercial or legal agreement regarding rights, obligations, or transactions.

Let us go deeper and try to build an understanding on negotiation. Elaborating on the above definition, it may be reasonable to assume that negotiation happens to reach from an “Initial State” to an agreed “Final State” following the steps given as under: -

Initial State (Pre-Negotiation Arrangement) à Negotiation (amongst Stakeholders) à (Binding) Agreement à Execution (of Agreement) à Final State (Post Agreement Arrangement)

We may call this as Negotiation Cycle and can be represented as following 5 steps: -

Initial State à Negotiation à Agreement à Execution à Final State

The initial state is the given (AS-IS) scenario. Usually there are problems in the initial state and negotiation takes place to solve the problems by executing a mutually agreed agreement to reach a final state (TO-BE). This final state is expected to solve the problems (which were being faced when at the initial state).  

In the next section, we will dig deeper into a possible process any negotiator may consider to bring all the stakeholders to negotiate and converge to an agreement.


                                                                 (2)

The 5 Step Negotiation Process in Reference to Negotiation Cycle

In this section, we attempt to develop step by step process to help professional (and non-professional) negotiators, while conducting negotiations amongst stakeholders. This process is executed under "Negotiation" step in the Negotiation Cycle. We may call this process as Negotiation Process and the steps in the process are as under: -

Clarity à Trust à Risks à Conflicts à Convergence

 These steps are explained under the following points: -


1.    Clarity and Conviction for Intended Benefits (Clarity)

A negotiator must be convinced that there is a merit in reaching Final State from Initial State in the Negotiation Cycle. So, to say, that the transformation (reaching from Initial State to Final State and sustaining at the Final State), which is brought about by the transition (executing a binding agreement) has an advantage (which can also be considered as solving problems being faced in Initial State). The endeavour to go through the Negotiation Cycle is the motivation to reach position of advantage and benefit out of it. The promise of this motivation is expected to foster and to bind the agreement amongst the stakeholders.

Thus, a negotiator must first get a thorough understanding on the mechanics of operations in the Initial-State to the mechanics of operations in the Final-State and more importantly sustainability of Final-State to produce intended advantage for the stakeholders.

This clarity is most important as a negotiator needs to be perceived as convincing, credible and knowledgeable expert, who supports stakeholders taking positions in the interest of transformative advantage without any other motive.

Initially the negotiator may present the idea in letter and in spirit that fuels the efforts to traverse the Negotiation Cycle. All the queries, confusions and information relevant to stakeholders be addressed at this step.

 

2.    Mutual Trust and Intent to Execute (Trust)

Once things look clear to the stakeholders, trust is the next important factor to take the negotiation forward.

The output of negotiation is agreement amongst stakeholders (as per Negotiation Cycle). This is followed by execution than to reaching the Final-State and eventually to reaping the outcome in terms of sustaining at Final-State for perceived advantage.

In this process, assurance of holding-on to the agreed positions in the agreement by stakeholders and going ahead keeping commitment to play respective part during the execution are the two major apprehensions a negotiator has to deal with during any negotiation. Further, keeping all the stakeholders convinced that execution will continuously be focused on achievement of outcome could be challenging.

Trust amongst stakeholders keep the negotiation engaged towards a prospective agreement. Developing mutual trust amongst the stakeholders is a subjective matter and may greatly get influenced by socio-cultural norms or impactful legal dispute resolution system in place.

However, a negotiator may assess the stakeholders for any issue with trusting fellow stakeholders or the viability of proposed benefits in the end of the Negotiation Cycle. All the possible efforts for alignment must be done at this stage. In case, it is observed that there is an extremely vulnerable stakeholder (with respect to issues pertaining to trust), the negotiator may try to build address concerns of this stakeholder with others in a consensual way.

Sometimes, a possibility of introducing a mechanism for compensation to extremely vulnerable or risk averse stakeholders in case of unforeseen circumstances can be helpful.

 

3.    Articulation of Ground Realities and Realistic Prospects with a Neutral Position (Risks)

Once clarity on negotiation cycle and mutual trust has been achieved it is worth deliberating on execution (as per negotiation cycle) and executional risks.

The proposition of benefits of transformation looks promising but the ground realities to reach to a position to reap the benefits are often grounded on rough realities coupled with unforeseen risks hidden in futuristic promises.

A negotiator may maintain information symmetry and neutral position in articulating the risks associated with the agreement, execution plan, sustainability of Final-State and with reaping the benefits (through the advantages achieved after reaching to Final-State).

Mitigation to known risks be allowed to be part of negotiation discussions.  To address unknown risks, agreement on guiding principles be finalized so that in case of occurrence of such unknown risks, a resolution be achieved with minimal conflicts amongst the stakeholders.

A transparent monitoring plan with options to renegotiate in certain circumstances (like – situation get unfair to any stakeholder with respect to spirit of the initial agreement) could be helpful. A communication plan tuned to the monitoring plan also helps in keeping stakeholders adequately informed with the proceedings and guide them with possibilities in foreseeable future.

 

4.    Reduce Differences to Core Conflicts and map them to Vested Interests (Conflicts)

Once the deliberations on execution and executional risks have been rigorously conducted, the entire negotiation cycle is expected to be crystal clear to all the stakeholders. Probably, this is good time to start understanding the differences amongst the stakeholders.

Differences are natural and more so when stakes are high on an endeavour. Differences amongst stakeholders may be reflection of underlying conflicts. Therefore, a negotiator may try reductional approach to breakdown differences to lesser numbers of conflicts and conflicts to still fewer numbers of core conflicts.

Core conflicts can be understood in terms of vested interests. The negotiator may decode the core conflicts and objectively link them to vested interests but may refrain from any attachment to the interests of stakeholder. It is better to remain at a distance and illustrate the facts in polite, firms and indifferent way. The negotiator be seen as solely concerned about the achievement of intended benefits by making the agreement to happen with mutual consensus.

While understanding the vested interests and working towards resolution be left to the stakeholders themselves, a negotiator may try to help in rational understanding of interests and related consequences to the larger objective of the negotiation cycle. Illustrations on how competitive interests can be made collaborative and how to shift attitude towards interests from compromising to accommodative could present helpful guidance.   

 

5.    Allow Deliberations to Foster an Agreement (Convergence)

Having elaborated on clarity, trust, risks and major areas of conflicts with utmost honesty and complete fairness, a negotiator has set the stage for open discussions, debate and deliberations amongst the stakeholders to converge at in-principle agreement.

By now, all the stakeholders can see through the end-to-end negotiation cycle with clarity and understand the dynamics of negotiation cycle with the help of above-mentioned negotiation steps. They have developed a thorough understanding of core conflicts arising from vested interests (or interest groups). Thus, they are well prepared to bid for investment, positions and stakes in the endeavour.

In this stage stakeholders conduct give and take of vested interests to manage conflicts, dissolve differences and eventually come to a broad stake holding arrangements with an outline of roles, responsibilities and duties to be performed for realization of promise of transformation the negotiation cycle proposes.

It is not unlikely that power dynamics and social positioning may have had influence in resolution of vested interests, stake-holding pattern and conditions of the agreement. Sometimes, these factors may have shaped the agreement in such a way, which may not be in the best interest of outcomes of the exercise being undertaken though the negotiation cycle or even may not be as per the prevailing notion of justice. However, in the capacity of a negotiator, it is better to ignore such aspects leaving them to be handled by the society at large.  

Once an in-principle agreement has been reached amongst the stakeholders with broad agreement on conditions, provisions and schedules of the agreement, a draft agreement with finer details be prepared (with due consideration to legal, commercial, social aspects) and put-up for formal approval by stakeholders after following the due process.



/****************************/ 


Saturday, December 20, 2025

How to Write a Better Functional Requirements Document?

 

 

(Image Reference  Image created using AI through ChatGPT) 


Unaddressed gaps in functional requirement document is one of the most common causes for failed IT (Information Technology) projects (intended for Strategic Business Transformation). In this blogpost, I have tried to highlight some points, which (if given consideration) may help in improving capture and documentation of requirements for any major IT project. These are: -

1. Story of Transformation is more about the Organization and less about the Technology - "Information Technology" implements “Information Management” as per "Information Design" for any organization. Therefore, it may be noted that clarity in organizational information design and in execution of this design (through information management) are more important than underlying technology (which is merely a tool to implement design through electronic means).

2. An Organization is a System of Systems - It may be helpful to express an organization as an institutionalized entity having responsibility of pre-defined work to deliver (tasks with activities) with the help of an organizational structure (organizational chart of designated officials with respective responsibilities and associated authorities) and a set of governing rules (for systematic operation of organization to deliver work with institutional obligation to remain just, fair and transparent in conduct). Thus, an organization may be viewed as a system having dependencies on many (sub) systems.

3. Understanding the Information Design behind Organizational Practice of Information Management - Information Design within an organization could be viewed as a template for rule-based exchange of information across the organizational structure intended to operationalize delivery of work (as expected from the organization). Implementation of information design through information management allows administration of information in such a way that appropriate and authentic information is available within the organization in timely manner.

4. Information Management is a Specialized and Critical Service to drive Organizational Operations - Success of a "Functional Requirement" document lies in representing information management as a structured entity logically connected with organizational workflows, which are executed by officiating officials (human resources working as per (usually) hierarchical roles with defined authorities and responsibilities). Thus, information is serviced to facilitate organization (through underneath organizational structure) to work in accordance with the needs of intended objectives.

5. Three Aspects to Organizational Information - Three broad aspects of information management within an organization could be considered as - information capture, information flow and information storage.

6. Objectivity on Transformative Information Technology Project is Important – Since any transformative information technology project is essentially an organizational endeavour to change organizational Information Design (usually) to support a mid-to-long term strategy (targeted at operational changes with the motive of business prospects), it is important to have objectivity embedded in the design of such a project.

It could be helpful to develop a ‘Mission Paper’ (usually aligned to Organizational Vision) on Strategic Organizational Transformation (including Strategy, Feasibility, AS-IS & TO-BE Guidance) to make the objectives of endeavour clear, precise, tractable and measurable. The ‘Mission Paper’ could become input to project charter for the associated transformative project(s).

7. Assess the Need for Engaging Workforce on Transformational Endeavours – Try to assess understanding and existing capacity of the workforce to take-on the transformational journey. Give heed to needs to educate end-users and to bring them onboard into the project so that they get actively engaged to become prospective performers in the TO-BE scenario implementation. Accommodate requirements for holding sensitization sessions and discussion sessions with end-users to build internal consensus on upcoming change. Precise understanding of AS-IS Scenario & TO-BE Scenario (with respect to work, structure, rules and information management) and understanding of intended organizational benefits to get intended strategic benefits out of transformational endeavour engages the workforce and at the same time wins credibility and trust of senior management in the eyes of workforce.

8. Traverse all the Actors and Paths in Work-Flow and associated Processes – Try to design Work-Flow for every entity (actor) under organizational structure taking TO-BE Scenario in consideration (also include actors at interfaces to the organization – (say) stakeholders outside the organization - like customers / suppliers / prospective-candidates interested in joining the organization / partner-institutions to an organization). Traverse all the possible paths in every workflow. Diagrammatically represent Workflows precisely highlighting the most important paths critical to delivery of prime responsibility of the organization and highlighting associated paths addressing quality concerns of the most important path(s).

9. Design of Wireframes Helps – With agreed workflows as input, designing wireframes to ensure UI / UX (User Interface and User Experience) helps reducing any confusion, any apprehension or any operational concerns in the minds of user community (while operating under TO-BE scenario). Expectations from new applications in the minds of decision makers also gets a reality check while traversing through TO-BE wireframes. With approved wireframes the application development team also feel confident about clarity of requirements.

10. Include Monitoring and Control of Information under TO-BE Scenario – It is good to incorporate requirements for monitoring and control of information. While designing an Information-Management system including reliable information capture, logical information flow, modular information storage requirements incorporating authorized accessibility of organizational information are important but monitoring organizational information for availability, accuracy, completeness and with prompts for finding related information (or provision for knowledge management) is equally important.

11. Keep in Perspective the Next Steps to follow after the Requirement Document – It is advisable to not to lose the sight of end-to-end project while doing capture of requirements. It is much better to keep the other teams and stakeholders on-boarded with the proceedings during the capture of requirements.

Some expected upcoming activities after ‘Requirements Document’ could be: -

a.     Technology Design to support finalized UI-UX design. Technology Design may include: -

                                i.     Database Design

                              ii.     Application Design (Development of Forms & Reports, Incorporation of Business Logic - for Business Operations and Business Analysis)

                            iii.     Technical Architecture (Platform - Technology Stack, Integration, AI Tools, Database Implementation).

                            iv.     IT Infrastructure and Connectivity Requirements.

                              v.     IT Governance (including - Data Retention Policy, Security Policy and Certifications, Quality and SLA, Operation and Maintenance).

b.    Cost Estimation: -

                                i.     Make or Buy / Develop or Customize considerations

                              ii.     Procurement and Operationalization costs

                            iii.     Continuous Business Support (Operation and Maintenance) for a suitable period of time.


           

/**********************/


The above-mentioned points relate to a view of system design for an organization. In a way this section is an attempt to present a context to above jotting and may be considered as an appendix to the blog-post.

 

System Design – Some Points to Consider

Designing an appropriate system tuned to cater to needs of an organization in effective and efficient manner could be complex task requiring collaboration with experts from technology and from sector / domain.

There may not be a general rule to do the design. However, the following points may be helpful. These are just a rough personal jotting for illustration purposes only. This is broadly a sketch that comes to my mind, whenever I have to deal with system design for an organization.

1.     Objective(s) of an organization

2.     Constitutional, Legal and Commercial obligations to the Organization

3.     Organizational Execution Strategy and Plan (to meet the objectives)

4.     Supporting Functions to Facilitate Organizational Execution

5.     Design of an Organization

a.     Structure

b.     Command Chain & Span of Control

6.     Functional Design

a.     Rules to execute and run the organization (Procedures)

b.     Authority and Responsibilities / Duties

c.     Command Chain and Span of Control

d.     Assets, Resources and Ownership

e.     Checks and Balances

f.      Organizational Work-Flow (Component Wise Orchestration of Execution Components)

7.     Information Design

a.     Information - a non-tangible asset to the organization

b.     Work-Flow - Execution performed under Organizational and Functional Design

c.     Information Dynamics - Information Capture, Information Flow & Information Processing to support the Work-Flow

d.     Information Classification and Information Authorization for executing the Work-Flow

                                                    i.     Rule driven Possession and Access of Information as per Organizational Structure and Command Chain

e.     Information Assurance (Controls for Accuracy and Integrity)

8.     Information System Design

a.     Automation Requirements for Efficient Execution (Strategy)

b.     Operational Requirements for Effective Automation

c.     Service Design (connecting people-props-process through modular access to (say) information capture (forms) and information analysis (reports)) to cater to Operational Requirements

d.     Provisioning of Services in accordance with Service Design through Technology

9.     Information Technology Design - Technology Selection as a Solution to Services to be Provisioned to cater to Operational requirements of the Organization

a.     Technology Architecture (usually presented in Component Wise View) - Operational Design optimized to efficient use of available resources keeping in view the long-term Information Technology Strategy of an organization – This may include considerations in terms of

                                                    i.     System Distribution (say - Monolithic / Microservices)

                                                  ii.     System Scalability

                                                 iii.     System Availability

                                                 iv.     System Quality and Quality Attributes

                                                  v.     System Upgradation and Support Requirements

                                                 vi.     Interaction of System with external Heterogenous Systems

                                               vii.     Support for Protocols and Stacks

                                             viii.     Support for interfaces (Mobile, Web)

                                                 ix.     Support for enhancements (AI, Data Analytics

                                                  x.     Access to External Data in different formats

                                                 xi.     Communication across Components

                                               xii.     System Health Monitoring and Control

                                             xiii.     Back-Up and Recovery Mechanism

                                             xiv.     Disaster Recovery

b.     Design of Applications (to cater to service design)

c.     Application Stack Selection (operationalization, compatibility, cost and maintainability)

d.     Design of Databases (requirements of data and transactional characteristics of operations)

10. Information Technology Infrastructure Design – Electronic Infrastructure to support Technology Design

a.     Servers and Storage Arrangements (On-Premises / Cloud / Virtualization / Containerization)

b.     Sizing of Servers / Storage and Scalability

c.     Requirements of Processing (Speed, Distribution)

d.     Network Requirements

 

 

/*****************************/