Adapt Consulting Company – Page 37 – Consult CoCreate Deliver

Which hat have you agreed to wear?

Post author By timhjrogers
Post date 6th February 2024

It’s feasible for an individual to take on multiple roles in a project, but it’s crucial for everyone involved to clearly understand their specific role and the expectations associated with it. Misunderstandings and assumptions about responsibilities can lead to issues, emphasizing the importance of clear communication regarding roles, scope, and obligations, especially with contracted parties, for the success of the project.

Project management often encompasses more than just overseeing tasks; it can involve aspects of product development, team management, coaching, and consulting. This multifaceted role can lead to misunderstandings about its scope. To clarify, one might compare a project manager to an orchestra conductor who doesn’t play the instruments or choose the music but ensures the performance runs smoothly. In contrast, a product owner or developer is akin to the composer, creating the content but not conducting the performance.

Project assurance is another distinct role, focusing on addressing business and technical risks to deliver the project on time, within budget, and according to specifications, ensuring it meets both narrow technical and broad business requirements. This is separate from the day-to-day management tasks of a project manager, which include managing people, tasks, funding, and reporting on progress, as well as facilitating discussions on changes.

Understanding these roles – project manager, product owner, project assurance, along with others like Scrum master, coach, and consultant – helps clarify responsibilities and allows for the creation of hybrid roles to suit specific needs, acknowledging the reality that individuals often wear multiple hats in project execution.

Project Assurance: Ensures projects align with business standards and objectives while managing risks and quality.
Project Management: Oversees the planning, execution, and completion of a project, ensuring it meets its goals, deadlines, and budget.
Scrum Master: Facilitates and supports a Scrum team, ensuring adherence to agile principles and practices for efficient project delivery.
Product Owner: Defines the vision and priorities for the product, representing the end-user’s interests and requirements.
Coach: Guides teams and individuals in developing their skills and achieving their personal and professional goals.
Consultant: Provides expert advice in a specific area to help organizations improve their performance and achieve their objectives.
Developer: Builds and creates software applications or systems based on technical design and specifications.
Test Manager: Oversees the testing phase of the development process, ensuring the product meets quality standards and functions as intended.

Both PRINCE2 (Projects IN Controlled Environments) and Scrum Agile methodologies define specific roles that contribute to the structure and success of project management. These roles are designed to ensure clear communication, responsibility, and accountability.

Here’s an overview of key roles in each methodology beyond those already mentioned:

PRINCE2 Roles

Executive: The single individual responsible for ensuring that a project meets its objectives and delivers the projected benefits. The Executive represents the interests of the organization funding the project.
Senior User(s): Represents the interests of those who will use the project’s outputs. Senior Users are responsible for specifying the needs of those who will use the project’s products and for the user acceptance of the final product.
Senior Supplier(s): Represents the interests of those designing, developing, facilitating, procuring, and implementing the project’s outputs. This role is accountable for the quality of products delivered by the supplier(s).
Project Board: Comprised of the Executive, Senior User, and Senior Supplier, the Project Board is responsible for providing overall direction and management of the project.
Project Manager: Oversees the planning, delegation, monitoring, and control of all aspects of the project, and the motivation of those involved, to achieve the project objectives within the expected performance targets for time, cost, quality, scope, benefits, and risks.
Team Manager: Responsible for the production of the project’s products, managing the production team, and reporting to the Project Manager.
Project Support: Provides administrative services to the Project Manager, dealing with project paperwork and offering guidance about the PRINCE2 methodology.

Scrum Agile Roles

Development Team: A group of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. A Development Team is made up of 3–9 individuals with cross-functional skills who do the actual work (analyze, design, develop, test, technical communication, document, etc.).
Product Backlog Refinement: While not a role, this is a key activity in Scrum involving the Product Owner and the Development Team. The activity is where the Product Backlog items are reviewed and revised. It is a collaborative effort to ensure that the backlog remains populated with items that are relevant, detailed, and estimated.

Additional Agile Roles (Not Specifically Scrum)

Agile Coach: Helps teams implement and improve Agile practices and methodologies. An Agile Coach is more experienced than a Scrum Master and often works with multiple teams or at the organizational level.
Release Manager: In some Agile implementations, a Release Manager is responsible for the process of managing, planning, scheduling, and controlling a software build through different stages and environments; including testing and deploying software releases.

Both PRINCE2 and Scrum Agile methodologies emphasize the importance of clearly defined roles for the successful delivery of projects. Each role has specific responsibilities and is crucial for the smooth execution of project tasks and achievement of project objectives.

Tim HJ Rogers
Consult | CoCreate | Deliver

I support people and teams to grow, perform and succeed unlocking potential as a partner Consultant, Coach, Project and Change Manager
Together we can deliver projects and change, and improve the confidence, capacity, drive and desire of the people I work with.

#people #process #performance #projects #programmes #pmo #change #processimprovement #projectmanagement #changemanagement #workshops #mediation #coach #icfcoach #mentor #facilitation #training #jersey #channelislands

Uncategorised

The perils of pricing innovation and the dangers of fixed-price promises

Post author By timhjrogers
Post date 5th February 2024

In the dynamic landscape of business, where innovation and agility are at the forefront, the approach to pricing, especially in contracts involving novel or complex deliverables, is fraught with challenges. This is particularly true for projects within lean startups or those with a significant technological innovation component, where there is scant historical data to inform cost and time estimations. The allure of fixed-price contracts, with their promise of budget certainty, can quickly become a perilous pitfall for both providers and clients when venturing into uncharted territories of product development.

The Complexity of Novel Projects

When dealing with projects that aim to bring something entirely new to the market, or when the project team is navigating the development process for the first time, the uncertainty multiplies. This dual novelty—of the product itself and the team’s inexperience with it—complicates the ability to accurately predict the project’s trajectory. Unlike replicating or slightly modifying existing products (like baking another chocolate cake following a well-trodden recipe), innovating (such as creating a never-before-seen dessert) lacks a clear path or precedent, making fixed pricing not just difficult but potentially misleading.

The Dangers of Fixed-Price Promises

Fixed-price contracts, while seemingly offering a safety net of predictability, often lead to a minimization of committed deliverables within that price cap. Anything beyond the initial scope typically triggers change control processes, inflating costs unpredictably. This scenario is not uncommon; vendors may underbid to win contracts, fully aware that the actual requirements will exceed the scope of their initial quote. They rely on subsequent change requests to recoup costs and secure profits, exploiting the gap between the client’s expectations and the evolving reality of the project’s needs. This practice not only strains client-vendor relationships but also introduces significant risk and uncertainty into projects, countering the very premise of fixed-price stability.

The Gap Between Hope and Reality

The stark difference between the hopeful optimism of a fixed-price contract and the practical realities of project execution cannot be overstated. The initial low price becomes a mirage as the true complexity and evolving nature of the project come to light, often leading to a reassessment of needs and a surge in costs due to changes. This gap represents not just a financial or operational challenge but a fundamental misunderstanding of the nature of innovation. Innovation, by its very nature, is exploratory and uncertain, making any attempt to rigidly define its cost and timeline at the outset a gamble.

Navigating Forward

The key to managing the inherent uncertainties of innovative projects may not lie in avoiding fixed-price contracts altogether but in fostering a deeper understanding and flexibility within them. This could involve:

Dynamic Pricing Models: Adopting pricing models that allow for adjustments based on project milestones, emerging requirements, and unforeseen challenges.
Transparent Communication: Ensuring open lines of communication between clients and vendors to manage expectations and address changes proactively.
Collaborative Risk Management: Sharing the risks associated with innovation, possibly through contracts that balance fixed and variable pricing elements based on project outcomes.

In conclusion, while fixed-price contracts offer the allure of budget certainty, their application in the context of innovation requires careful consideration. The unpredictable nature of developing novel products or services demands a more flexible, transparent, and collaborative approach to contract structuring. By acknowledging the perils of fixed pricing in innovation, businesses can better navigate the complexities of bringing new ideas to fruition, ensuring that the journey from concept to reality is marked by partnership rather than contention.

Tim HJ Rogers
Consult | CoCreate | Deliver

Uncategorised

A Balanced Approach towards a reliance on Process for Success

Post author By timhjrogers
Post date 4th February 2024

In the rapidly evolving landscape of project management and coaching, understanding and adapting to various methodologies is crucial. Whether navigating through the structured phases of the Waterfall model or the iterative cycles of Agile, the essence of success lies in leveraging these processes to our advantage. However, in a world characterized by Volatility, Uncertainty, Complexity, and Ambiguity (VUCA), striking the right balance between process adherence and flexibility becomes paramount.

Waterfall vs. Agile: A Brief Overview

Waterfall is a sequential project management approach where each phase must be completed before the next one begins. This method is known for its structured nature, making it suitable for projects with well-defined requirements and where changes are less likely to occur.

Agile, on the other hand, is an iterative approach that promotes continuous collaboration and flexibility throughout the project. It allows for adapting to changes quickly, making it ideal for projects where requirements are expected to evolve.

Understanding VUCA

The VUCA framework highlights the challenges and opportunities presented by Volatility, Uncertainty, Complexity, and Ambiguity. It underscores the need for agility and adaptability in decision-making processes, urging leaders and teams to develop resilience and strategic foresight.

The Gambler’s Fallacy and the Idea of Double or Quits

The Gambler’s Fallacy is the erroneous belief that if something happens more frequently than normal during a given period, it will happen less frequently in the future, or vice versa. In project management, this fallacy can manifest in risk assessment and decision-making, leading to flawed strategies based on past outcomes rather than rational analysis.

The concept of Double or Quits is a risky gamble where one continues to double the stake in the hope of recouping lost resources or achieving a significant gain. This approach can be perilous in project management, as it may lead to escalating commitments to failing courses of action.

Philosophical Views on Process

Processes are essential for providing structure and clarity in both project management and coaching. They facilitate communication, coordinate resources, and define roles, goals, and controls. However, there’s a philosophical debate on the extent to which processes should govern our actions. While they are invaluable for governance and ensuring that activities are carried out systematically, there’s a risk of becoming overly reliant on them, potentially overshadowing the ultimate objectives.

In project management, whether in a Waterfall or Agile environment, the process serves as a roadmap. Yet, the dynamic nature of today’s VUCA world necessitates a shift towards more agile methodologies, where minimum bureaucracy and overhead allow for flexibility and rapid response to change.

Similarly, in coaching, processes like the GROW model offer a structured approach to achieving goals. Yet, the essence lies in the co-creation of meaningful plans that are responsive to the client’s evolving needs.

The Balance

The key is to find a balance where the process aids rather than hinders progress. Lean methodologies and the concept of “Genchi Genbutsu” (go and see) advocate for a reality-based approach, emphasizing the importance of observing and understanding the situation firsthand rather than relying solely on reports and dashboards.

In conclusion, while processes are indispensable for organization and efficiency, their ultimate purpose is to serve the project or coaching objectives, not to become an end in themselves. In our VUCA world, the ability to adapt, to see beyond the process, and to focus on outcomes is what will define success. Let us embrace processes, but also remain vigilant to ensure they do not become our shackles.
Tim HJ Rogers
Consult | CoCreate | Deliver

I support people and teams to grow, perform and succeed unlocking potential as a partner Consultant, Coach, Project and Change Manager. mTogether we can deliver projects and change, and improve the confidence, capacity, drive and desire of the people I work with.

Uncategorised

Business Plans And Planning

Post author By timhjrogers
Post date 2nd February 2024

1. What Typically Goes into a Business Plan

A business plan is a comprehensive document that outlines the foundation, strategy, and financial projections of a business. It serves as a roadmap for the business’s growth and is often used to secure funding from investors or lenders. A typical business plan includes:

Executive Summary: An overview of the business, including its mission statement, product or service offerings, and basic information about the company’s leadership team, employees, and location.
Company Description: Detailed information about the business, including the problems it solves, its target market, and competitive advantages.
Market Analysis: Research on the industry, market size, expected growth, market trends, and analysis of the competition.
Organization and Management: Information on the business’s legal structure, management team, and the organizational structure.
Service or Product Line: Details about the products or services being offered, including information on product lifecycle, intellectual property, and research and development activities.
Marketing and Sales Strategy: How the business plans to attract and retain customers, including pricing, promotions, sales channels, and sales strategies.
Funding Request: If seeking financing, details of the funding requirements, future financial plans, and proposed use of funds.
Financial Projections: Includes income statements, cash flow statements, and balance sheets for the next three to five years. This section should also include a break-even analysis.
Appendix: An optional section that can include resumes, permits, lease agreements, legal documentation, and other relevant documents.

2. Compare a Business Plan with a Business Strategy

Business Plan: This is a document that outlines the operational and financial objectives of a business and contains detailed plans and budgets showing how the objectives are to be realized. It is very detailed and usually covers a short to medium-term period (1-5 years). It is often used to pitch to investors or banks for funding and serves as a roadmap for business operations.

Business Strategy: This refers to the high-level plan or set of decisions that aim to achieve competitive advantage and effectively manage resources to achieve long-term goals. It’s more about the direction in which the business wants to go and how it will compete successfully in the market. Business strategy is more about the “why” and “what” part of the goals, focusing on long-term growth and sustainability rather than the detailed “how” of day-to-day operations.

3. Compare a Business Plan with Business Canvas

Business Plan: As described, it’s a detailed document covering various aspects of the business, including market analysis, financial projections, and marketing strategies. It’s text-heavy, detailed, and designed to be presented to external parties like investors and banks.

Business Model Canvas (BMC): This is a strategic management template for developing new or documenting existing business models. It’s a visual chart with elements describing a company’s value proposition, infrastructure, customers, and finances. The BMC helps businesses to align their activities by illustrating potential trade-offs in a more accessible and understandable way. Unlike the traditional business plan, the BMC is succinct, covering key components of a business on a single page, which makes it easier to understand and adjust quickly.

In summary, while a business plan provides a detailed blueprint of how a business intends to achieve its goals, including financial forecasts and detailed market analysis, a business strategy outlines the overarching approach to winning in the market. Meanwhile, the Business Model Canvas offers a high-level, visual overview of the key elements of a business, focusing on how various parts of the business fit together rather than on the detailed operational or financial planning.

Download Jersey Business’ Business Plan Template
https://www.jerseybusiness.je/guides/business-plan-template/

Business Model Canvas (BMC)
https://en.wikipedia.org/wiki/Business_Model_Canvas
https://medium.com/seed-digital/how-to-business-model-canvas-explained-ad3676b6fe4a

Tim HJ Rogers
Consult | CoCreate | Deliver

ABOUT MY BUSINESS
My approach is to blend my expertise [Consultant, Coach, Project and Change Manager] with the strengths of our partners, ensuring that we consistently deliver high-quality, tailored solutions to our clients. My Associate approach not only fosters a dynamic and collaborative environment but also maximizes the value we deliver to our clients and partners alike. There is an optimum combination of factors or qualities which help people and organisations transform. It is a blend of listening, challenging and sharing and comes from expertise, experience, curiosity and a passion to perform. I deliver projects and change, and improve the confidence, capacity, drive and desire of the people I work with.

Uncategorised

Navigating the “What” and “How” in Agile User Stories: A Guide for Complex Domains

Post author By timhjrogers
Post date 2nd February 2024

In the world of Agile software development, crafting user stories is an art that balances between specifying the needs (the “what” and “why”) and leaving room for technical creativity (the “how”). This balance is crucial for fostering innovation, leveraging developer expertise, and ensuring adaptability. However, when dealing with complex domains, such as insurance or finance, the traditional approach to user stories can present challenges. How do we ensure that our user stories are clear and informative without dictating the solution? Let’s explore.

The Essence of User Stories

User stories serve as a bridge between the end users’ needs and the technical solutions that fulfill those needs. They are fundamentally about the “what” and “why” – what the user needs and why they need it. This focus encourages a collaborative approach to problem-solving, inviting developers to contribute their technical insights to find the most effective solutions.

The Challenge in Complex Domains

In domains where technical teams may not have inherent domain expertise, the risk of misinterpretation or oversimplification of user stories increases. The intricacies of insurance policies, financial regulations, or healthcare protocols can’t always be intuitively understood without detailed explanation. This gap necessitates a nuanced approach to writing user stories, one that provides clarity without compromising the Agile principle of empowering teams to determine the “how.”

Striking the Right Balance

To navigate this complexity, consider these strategies:

Provide Domain Context: Enhance user stories with sufficient background information. This doesn’t mean dictating the solution but rather ensuring the development team understands the domain-specific challenges and terminology.
Define Clear Acceptance Criteria: Detailed acceptance criteria can offer a roadmap of what success looks like without prescribing how to get there. This includes outlining business rules, data requirements, and expected outcomes.
Leverage Supporting Documentation: Where necessary, supplement user stories with documents, diagrams, or explanatory sessions that bridge the knowledge gap, ensuring the team has a comprehensive understanding of the problem space.
Foster Collaborative Discovery: Engage in practices like “Three Amigos” meetings, where business analysts, developers, and testers collectively explore and refine user stories. This collaboration ensures a shared understanding and innovative problem-solving.
Incremental Detailing: Offer detailed insights into the “how” through iterative discussions, backlog refinement, and sprint planning, rather than embedding it directly into the user story. This approach maintains flexibility while ensuring the team has the necessary information to proceed.

Conclusion

In complex domains, the art of writing user stories demands a careful balance between providing enough context to ensure clarity and leaving sufficient room for technical innovation. By focusing on the “what” and “why,” supplemented with strategic detailing where necessary, we can empower Agile teams to excel even in the most intricate fields. This approach not only leverages the collective expertise of the team but also ensures that solutions are both innovative and aligned with user needs, driving success in projects that span the spectrum of simplicity to complexity.

Tim HJ Rogers
Consult | CoCreate | Deliver

Uncategorised

Transformation Of Agile User Stories Into Executable Code In A Built Application

Post author By timhjrogers
Post date 2nd February 2024

The transformation of agile user stories into executable code in a built application is a structured yet flexible process, embodying the core principles of Agile methodology: collaboration, adaptability, and iterative development. This journey from concept to code involves several key steps, which can vary slightly depending on the specific Agile framework being used (e.g., Scrum, Kanban). However, the overarching process typically includes the following stages:

1. Creation of User Stories

Gathering Requirements: The process begins with the collection of requirements from stakeholders, including customers, users, and the development team. These requirements are then formulated into user stories, which are short, simple descriptions of a feature told from the perspective of the user or customer. A user story typically follows a simple template: “As a [type of user], I want [some goal] so that [some reason].”

2. Backlog Refinement

Prioritization and Refinement: User stories are added to the product backlog, which is a prioritized list of work for the development team. The team, along with the product owner, regularly reviews (refines) this backlog to prioritize the stories based on business value, urgency, and dependencies. This step ensures that the team always works on the most important features first.

3. Sprint Planning

Breaking Down Stories into Tasks: During sprint planning meetings (in the Scrum framework), selected user stories are moved from the product backlog to the sprint backlog. The development team then breaks down each user story into more manageable tasks. This step involves technical analysis and planning to determine how each story will be implemented.

4. Development

Coding: This is where the executable code is written. Developers take the tasks derived from user stories and start coding. This phase includes writing, testing, and reviewing code to meet the acceptance criteria defined in the user stories.

5. Continuous Integration and Testing

Testing: Alongside or immediately after development, testing is conducted to ensure the code meets the required standards and behaves as expected. This often involves automated unit tests, integration tests, and manual testing processes. Continuous Integration (CI) practices are commonly used, where code changes are automatically built, tested, and merged into a shared repository frequently.

6. Review and Feedback

Sprint Review/Demo: At the end of each sprint, the team demonstrates the completed work to stakeholders. This is an opportunity to gather feedback and make any necessary adjustments. The focus is on delivering a potentially shippable product increment at the end of each sprint.

7. Retrospective and Continuous Improvement

Retrospective: After the review, the team holds a retrospective meeting to reflect on the sprint. They discuss what went well, what didn’t, and how processes can be improved. This continuous improvement is a cornerstone of Agile.

8. Deployment

Release: Once the code has been tested and approved, it is deployed to production. This may happen at the end of each sprint or at a different cadence, depending on the release strategy of the project.

9. Maintenance and Iteration

Iterative Development: Agile projects are iterative, meaning this process repeats, with the team going back to the backlog, selecting new user stories for the next sprint, and starting the cycle again. This allows for continuous delivery of value to the user and the ability to adapt to changes quickly.

Throughout these steps, collaboration among team members and stakeholders, as well as adaptability to feedback and changing requirements, are key. Agile emphasizes working software as the primary measure of progress, and this process, from user stories to executable code, is designed to achieve that goal efficiently and effectively.

Tim HJ Rogers
Consult | CoCreate | Deliver

Uncategorised

The Proof of Concept > The Prototype > The Minimal Viable Product

Post author By timhjrogers
Post date 31st January 2024

The Proof of Concept

At the outset of developing a minimal viable product (MVP), the initial step is establishing a proof of concept. This involves determining whether the idea addresses a need or desire for which customers are willing to pay. If the product doesn’t solve a problem or offer a benefit to the customer, the entire concept is likely to fail. Therefore, it’s essential to clarify what the product is, how it adds value, whether customers will desire it, and, crucially, if they are willing to pay for it. The product must be profitable enough to ensure business success. A proof of concept, akin to an architectural blueprint approved by the client before construction begins, is vital before any development. Investing a modest amount in getting this stage right can prevent significant financial losses from developing a product that doesn’t meet customer needs, lacks perceived value, or is priced inaccessibly.

The Prototype

Following a successful proof of concept, the next phase is creating a prototype. This step is about materializing the concept to see if it’s feasible in practice. Using an architectural analogy, it’s like examining a model village before full-scale construction. In software development, this might involve developing a few key features to test their effectiveness and value to the client. The prototype is basic, possibly unrefined, and lacks the full features, compliance, security, and validation of the final product. However, it should be sufficient to transform the proof of concept, which is an idea, into a tangible, albeit rudimentary, product.

The Minimal Viable Product

Once the prototype is approved, the next stage is enhancing it into a minimal viable product (MVP). The MVP, however, is not the final, comprehensive product. It’s an incremental step that adds more value and functionality but remains a basic version of what the product is envisioned to be. It adheres to the principle of delivering the essential features that customers are willing to pay for, often described by the 80/20 rule. The MVP is a functional product used regularly by users, but it’s not feature-complete. Initially, it might only perform a few tasks, but it should do them exceptionally well. Additional features and enhancements can be added later.

Tim HJ Rogers
Consult | CoCreate | Deliver

ICF Trained Coach
MBA Management Consultant
PRINCE2 Project Manager, Agile Scrum Master
AMPG Change Practitioner
Mediation Practitioner
BeTheBusiness Mentor
4 x GB Gold Medalist
First Aid for Mental Health
Certificate in Applied Therapeutic Skills

#ProofOfConcept #IdeaValidation #ConceptTesting #InnovationStrategy #StartupIdea #FeasibilityStudy #TechInnovation #BusinessConcept #PrototypeDevelopment #ProductDesign #InnovativeDesign #TechPrototype #PrototypeTesting #DesignThinking #EngineeringExcellence #ProductInnovation #MinimalViableProduct #MVP #LeanStartup #StartupJourney #ProductLaunch #EarlyAdopters #AgileDevelopment #MarketValidation

Uncategorised

GETTING STARTED, WITH START-UPS

Post author By timhjrogers
Post date 31st January 2024

Yesterday, I had the intriguing experience of collaborating with a startup entrepreneur on a tech project. In roles like project management and mentoring, we often overlook our own knowledge and expertise, assuming others have the same understanding. What’s fascinating about tech entrepreneurs, especially in startups, is their fresh, often untested ideas. Their limited experience can sometimes fuel innovative thinking, unhampered by conventional habits or past experiences.

One of the key challenges in this environment isn’t just providing mentorship or guiding the project to fruition. It’s about highlighting potential pitfalls and areas of caution. For instance, a startup’s success might hinge more on meeting financial milestones than on the sheer quality of the product. When developing a minimum viable product, there’s a common trap of trying to include too much, instead of focusing on what can realistically be demonstrated to backers in a short presentation, like a 45-minute session next Tuesday.

Maintaining a broad vision is important, but there’s also a critical need to concentrate on immediate tasks. It’s somewhat akin to performing emergency surgery on an athlete who, in the long run, is destined to win marathons. The focus might seem narrow now, but without addressing these immediate issues, the long-term goals remain unachievable.

This dynamic between short-term and long-term objectives, between what’s expedient and what’s necessary, is particularly distinct in startups compared to larger organizations. Bigger companies usually have more resources, time, and a buffer against risks, along with multiple projects that distribute their focus and mitigate risks. In contrast, startups are intensely personal, always under pressure, challenging, and almost invariably exhilarating to be involved with. They offer a unique and thrilling experience unlike any other in the business world.

Tim HJ Rogers
Consult | CoCreate | Deliver

Uncategorised

Creating the capacity for change – Got some spare time? (Good!)

Post author By timhjrogers
Post date 28th January 2024

In the dynamic landscape of organizational change, the transformation of the Ports of Jersey has been a pivotal project in my understanding and experience of the path to successful change management. This journey from a public sector entity to a thriving, integrated company underscores a vital principle: the necessity of creating capacity for change.

As a consultant and project manager, I’ve learned that change is not just an item on the agenda; it’s the agenda itself. The transformation journey at the Ports of Jersey, from integrating harbors and airports to altering its legal status, was a testament to this. The pivotal move? Senior management, led by then-CEO Doug Bannister, made a conscious effort to create space in their schedules for managing this change.

This approach had a dual impact. Firstly, it fostered a culture of delegation and trust, encouraging leaders to pass down responsibilities that could be better handled at different levels. This not only empowered teams but also cleared leadership decks for strategic thinking and decision-making.

Secondly, it highlighted the need for leaders to have the mental bandwidth to navigate the complexities of change. In an environment where being perpetually busy is often misinterpreted as a sign of indispensability, this shift in mindset was crucial. It emphasized that effective leadership is about being the architect of change, not just a cog in the machine.

However, this strategy was initially met with resistance. The misconception that spare capacity equates to redundancy had to be addressed. The realignment focused on the understanding that having the time to think, deliberate, and decide is a greater asset to leadership than constant busyness.

As the project manager for this transformation, I observed that without creating room for change, the success we achieved would have been unattainable. The unanimous support for the project upon completion was a testament to the effectiveness of our approach.

So, what can organizations take from this? Begin by carving out space for change. This January, let your first task be to clear a portion of your schedule specifically for managing and adapting to change. Treat it not as an add-on but as a fundamental component of your strategy. If change is just another block on your already teetering tower of tasks, the structure is bound to collapse.

Suggested Tasks/Habits:

Weekly Reflection: Dedicate time each week to reflect on change initiatives and their progress.
Delegate Effectively: Identify tasks that can be delegated to create space for strategic thinking.
Stakeholder Engagement: Regularly engage with stakeholders to align visions and address concerns.

Remember, change managed well is not just an alteration of what is, but a gateway to what could be.

Tim HJ Rogers
Consult | CoCreate | Deliver

Uncategorised

Embracing a Coaching Approach in Management: A Pathway to Enhanced Performance and Well-Being

Post author By timhjrogers
Post date 28th January 2024

In today’s rapidly evolving business landscape, the traditional models of management are being challenged and redefined. As organizations strive to foster environments that promote mental health, well-being, and engagement, the adoption of coaching skills by managers has emerged as a transformative strategy. This shift not only enhances personal development and performance appraisal but also aligns with the modern workplace’s emphasis on belonging, trust, and employee support.

The Evolution from Traditional Management to Coaching

Traditional management approaches have primarily focused on directing, controlling, and evaluating employees based on their output and productivity. However, this method often overlooks the individual’s personal growth and well-being, leading to a lack of engagement and motivation within the team. In contrast, a coaching style of leadership, as delineated by Gorman’s leadership styles, emphasizes personal development, performance through empowerment, and fostering an environment conducive to open communication and feedback.

These styles are based on elements of emotional intelligence and are designed to be flexibly applied depending on the situation, team needs, and organizational goals

Coercive Leadership: This “Do what I tell you” approach is the most authoritative, used in crisis situations or with problematic employees. It demands immediate compliance but can have a negative impact on the team’s morale if overused.

Authoritative Leadership: The “Come with me” or visionary approach motivates by persuading team members to buy into the leader’s vision for the future. It’s effective for providing clear direction and inspiring action toward common goals.

Affiliative Leadership: The “People come first” style focuses on creating emotional bonds and harmony. It’s beneficial in times of stress, or when team cohesion is needed, fostering positive relationships and improving communication.

Democratic Leadership: This style values the team’s input, asking “What do you think?” It’s useful for building consensus or getting valuable input from employees. However, it can lead to slow decision-making if overused.

Pacesetting Leadership: The “Do as I do, now” approach sets high standards for performance, with the leader expecting excellence and self-direction. It can increase productivity but may also overwhelm team members if the pace is too relentless.

Coaching Leadership: This “Try this” style focuses on personal development, offering guidance and encouraging employees to set and achieve their own goals. It’s effective for improving performance, fostering long-term professional development, and building strengths.

Goleman suggests that the most effective leaders are those who can skillfully switch between these styles as circumstances dictate, rather than relying on a single approach. The key is understanding the impact each style has on the emotional climate of the organization and its influence on performance.

Coaching vs. Managing vs. Mentoring

While these terms are frequently used interchangeably, they represent distinct approaches within the workplace:

Managing focuses on overseeing tasks and ensuring organizational goals are met.
Mentoring involves a more experienced individual guiding a less experienced person, often focusing on career and personal development.
Coaching, however, adopts a non-directive approach, encouraging individuals to find their own solutions, fostering a sense of agency, responsibility, and resourcefulness.

The Benefits of a Coaching Approach

Adopting a coaching approach in management can significantly impact an organization’s culture and performance. This method encourages employees to engage deeply with their work, fostering a sense of belonging and trust. It shifts the focus from merely achieving targets to enhancing well-being, engagement, and recognition of the individual’s contributions. Such an environment is conducive to retaining, motivating, and supporting staff, crucial for navigating the complexities of the modern workplace.

Why Enroll in Coaching Skills Courses?

For managers, enrolling in courses to improve coaching skills is not just about personal or professional development; it’s about transforming their approach to leadership. Training in coaching equips managers with the tools to:

Support mental health and well-being in the workplace.
Enhance performance through a focus on personal development.
Foster a culture of engagement, participation, and trust.
Encourage employees to take ownership of their roles and contributions to the team’s success.

Lifeline’s Tailored Approach to Coaching in Management

At Lifeline, we understand that each organization and individual is unique. Our coaching approach to management is designed to be flexible, incorporating the International Coach Federation (ICF) principles and competencies while adapting to the specific needs of the organization and its employees. We focus on making coaching skills relevant and practical for day-to-day management and leadership, ensuring that managers are not just overseers of work but facilitators of growth and well-being.

Conclusion

The transition towards a coaching style of leadership represents a significant shift in how organizations view performance, engagement, and employee well-being. By fostering an environment where individuals are encouraged to explore their potential and contribute meaningfully to their teams, businesses can unlock new levels of productivity and satisfaction. For managers and leaders looking to navigate this shift, investing in coaching skills development is a critical step forward. At Lifeline, we are committed to supporting this journey, tailoring our approach to meet the unique challenges and opportunities of your organization.

Tim HJ Rogers
Consult | CoCreate | Deliver