This document discusses visualizing excellence through paradigms, people, processes, and problem-solving. It outlines seven key improvement paradigms including defining quality through the customer, continuous incremental improvement, focusing on people, process-centric thinking, systems thinking, horizontal structures, and effective teams. It then discusses the four P's of excellence - paradigms, people, processes, and problem-solving and provides details on each.
HDR has acquired 32 firms in the past 10 years as part of its growth strategy. The average acquired firm has around 48 employees. HDR's acquisition process typically involves due diligence, management approval, and announcement. Integration of acquired firms is still a work in progress for HDR, but they are focusing more on change management training and having an on-site integration manager guide the process. Key lessons learned are that change management must be a priority from the beginning of acquisitions to minimize performance drops and maximize returns through improved productivity, quality, and morale. Communication is critical for successful integration and combatting natural anxiety that comes with change.
Lessons for Large Scale Lean and Agile Product Development - Atlassian Summit...Atlassian
1. The document discusses lessons for large scale lean and agile product management from a presentation at the Atlassian Summit 2012.
2. It provides a 10 point plan for transitioning to agile and emphasizes embracing change, focusing on people over process, and maintaining a sustainable pace of work.
3. The document also discusses techniques for improving backlogs through envisioning, estimating at a large scale, and coordinating feature and component teams.
The document discusses team development and high performance teams. It covers various stages of team development including forming, storming, norming, performing, and adjourning. Key aspects of effective teams are identified such as shared goals, clear roles, and open communication. Different team member roles are examined including those that show concern through contributing and clarifying, and those that cause frustration like dominating. The importance of teamwork and support are highlighted through lessons from geese who fly farther together through cooperation.
Agile and lean product development the fundamentalsRussell Pannone
The document discusses delivering value early and often through agile development practices to gain competitive advantages. It emphasizes cross-functional collaboration, continuous delivery of working software increments, early defect discovery, eliminating waste, and frequent feedback to improve. The goal is satisfying customers through adaptive teams that can sustain a constant development pace.
Improve the effectiveness of behavior based selection by incorporating competency modeling into selection and also training, performance management and succession planning
The document discusses the Improvement Kata as a framework for continuous process improvement. It describes the Improvement Kata as having four steps: 1) understand the direction of needed process improvement, 2) understand the current condition of the process, 3) establish a target condition for the process, and 4) use PDCA cycles to experiment towards the target condition. It then outlines the roles of the learner (process owner), coach, second coach, and team members in applying the Improvement Kata. The goal is to transform companies from a culture of reacting to a culture of continuous learning and improvement.
HDR has acquired 32 firms in the past 10 years as part of its growth strategy. The average acquired firm has around 48 employees. HDR's acquisition process typically involves due diligence, management approval, and announcement. Integration of acquired firms is still a work in progress for HDR, but they are focusing more on change management training and having an on-site integration manager guide the process. Key lessons learned are that change management must be a priority from the beginning of acquisitions to minimize performance drops and maximize returns through improved productivity, quality, and morale. Communication is critical for successful integration and combatting natural anxiety that comes with change.
Lessons for Large Scale Lean and Agile Product Development - Atlassian Summit...Atlassian
1. The document discusses lessons for large scale lean and agile product management from a presentation at the Atlassian Summit 2012.
2. It provides a 10 point plan for transitioning to agile and emphasizes embracing change, focusing on people over process, and maintaining a sustainable pace of work.
3. The document also discusses techniques for improving backlogs through envisioning, estimating at a large scale, and coordinating feature and component teams.
The document discusses team development and high performance teams. It covers various stages of team development including forming, storming, norming, performing, and adjourning. Key aspects of effective teams are identified such as shared goals, clear roles, and open communication. Different team member roles are examined including those that show concern through contributing and clarifying, and those that cause frustration like dominating. The importance of teamwork and support are highlighted through lessons from geese who fly farther together through cooperation.
Agile and lean product development the fundamentalsRussell Pannone
The document discusses delivering value early and often through agile development practices to gain competitive advantages. It emphasizes cross-functional collaboration, continuous delivery of working software increments, early defect discovery, eliminating waste, and frequent feedback to improve. The goal is satisfying customers through adaptive teams that can sustain a constant development pace.
Improve the effectiveness of behavior based selection by incorporating competency modeling into selection and also training, performance management and succession planning
The document discusses the Improvement Kata as a framework for continuous process improvement. It describes the Improvement Kata as having four steps: 1) understand the direction of needed process improvement, 2) understand the current condition of the process, 3) establish a target condition for the process, and 4) use PDCA cycles to experiment towards the target condition. It then outlines the roles of the learner (process owner), coach, second coach, and team members in applying the Improvement Kata. The goal is to transform companies from a culture of reacting to a culture of continuous learning and improvement.
Agile Developers Create Their Own IdentityAjay Danait
The document discusses building an agile organization culture and delivering agility through team agility. It focuses on agility assessment, coaching teams in agile practices like Scrum and XP, and transforming the organization. Specific services mentioned include software craftsmanship, agility in maintenance, agile enterprise architecture, and agility nurseries. The document also discusses assessing and improving team agility through techniques like value stream mapping and team chartering.
This document discusses key concepts in food and beverage management. It defines management as the process of planning, organizing, coordinating, staffing, directing, controlling, and evaluating. The management process aims to achieve organizational objectives through allocating resources and solving problems. Several management tasks are also outlined, including defining goals and objectives, developing action plans, organizing work assignments, effective communication, delegation, scheduling, recruiting and hiring, measuring performance, and assessing training programs. Daily activities for managers are listed such as developing budgets, addressing problems, coordinating special events, revising job descriptions, supervising employees, controlling costs, and conducting performance reviews. Managers must work with both primary and secondary groups to provide hospitality to guests.
The document discusses how companies can embrace change and drive innovation through software. It outlines a 4-phase framework for continuous process improvement using IBM Rational tools. Phase 1 involves establishing business objectives. Phase 2 prioritizes practices and defines an improvement roadmap. Phase 3 accelerates adoption with tools to improve requirements management, architecture, and development alignment. Phase 4 reports on results to identify further improvements. The framework aims to help companies optimize resources, deliver smarter products, and improve profits through incremental capability advances.
Normalizing agile and lean product development and aimRussell Pannone
The what, why, and how of agile and lean product (system-software) development and delivery is not one persons vision alone; to become reality it needs to be a "shared" vision through negotiation and compromise between individuals, the team and the organization.
The following is a set of norms for your agile and lean product (system-software) development teams to rally around and evolve.
1. The document discusses a case where an IT implementation project at a call center was facing challenges with select employee groups due to a lack of understanding of individual traits and how they impact change tolerance.
2. It introduces the concept of a "Worker's Microcosm" framework to gain a holistic understanding of workers' profiles, performance drivers, interests and how they align with job design and corporate systems before implementing changes.
3. Applying this framework through behavioral assessment tools during an ERP integration project helped identify the most compatible workers for specific process roles, improving performance synergy and project success.
The document provides an overview of Gemini Consulting's approach to leading organizational change. It discusses how the business environment is changing and requiring different approaches to change. Gemini's approach is grounded in tools developed from behavioral change insights that focus on changing individual behaviors through small groups. Gemini interventions create joint project teams of clients and consultants to serve as a safe environment to experiment with new ways of working and accelerate change. Gemini is evolving its approach to address continuous change and spreading learnings throughout organizations.
Agile2011 - What do we supposed to do with these managers now?skipangel
This document discusses the role of managers in agile organizations and options for how managers can adapt to agile ways of working. It suggests that managers transition from being directive leaders to being catalyst leaders who facilitate teams and create collaborative environments. Some ways managers can support teams mentioned are by reducing dependencies between teams, reducing technical and other debts, minimizing waste, and investing in learning. The document also notes that for agile to be successful, the entire organization needs to understand strategy, have a learning culture instead of a culture of fear, and optimize outcomes for the whole system rather than individual parts. It acknowledges that agile cannot address all challenges and is a significant organizational change and journey rather than a destination. Strong leadership is needed to make the
Refactoring the Organization Design (LESS2010)Ken Power
These are the presentation slides from a presentation I gave at the Lean Enterprise Software and Systems Conference 2010 (LESS 2010, http://less2010.leanssc.org/). The presentation is based around the paper I submitted that is published in the proceedings.
From the paper abstract:
Every organization has a design. As an organization grows, that design evolves. A decision to embrace agile and lean methods can expose weaknesses in the design. The concept of refactoring as applied to software design helps to improve the overall structure of the product or system. Principles of refactoring can also be applied to organization design. As with software design, the design of our organization can benefit from deliberate improvement efforts, but those efforts must have a purpose, and must serve the broad community of stakeholders that affect, or are affected by, the organization. Refactoring to agile and lean organizations demands that we have a shared vision of what the refactoring needs to achieve, and that we optimize the organization around the people doing the work.
The document discusses radical redesign in public services and caring roles. It explores moving from incremental to radical innovation by improving current services compared to mobilizing community resources and changing outcomes. Diagrams show moving from inside to outside the system and changing goals rather than means. The design process involves learning from users, generating ideas through co-design, and creating solutions that shift behaviors.
The document discusses group problem solving and facilitation. It describes the problem solving/team building (PS/TB) approach, which is an iterative, participative process that gets results by solving problems. The PS/TB approach involves 7 steps: 1) headlining the problem, 2) providing background, 3) generating ideas, 4) selecting ideas, 5) getting benefits and concerns, 6) working critical concerns, and 7) getting an action plan and next steps. The document also discusses effective facilitation skills and the role of the facilitator in leading a group through the problem solving process.
This document discusses the experience of a team at Huawei Technologies India in adopting Theory of Constraints (TOC) and Kanban practices. The team analyzed constraints through TOC to identify gaps like inefficient processes and lack of resources. They developed a future state tree to break conflicts with win-win solutions. This led them to adopt agile development using Scrum and share team members across components. Further TOC analysis identified challenges of reduced testing time and high workload bursts. The team addressed this by prioritizing work daily in one piece flow and using Kanban to control queues and delays. This improved efficiency by ensuring continuity of workflow.
This document summarizes an organization called Changefirst that provides change management consulting and training. It discusses Changefirst's People Centred Implementation methodology for helping organizations implement projects effectively by engaging people and building skills to adapt to changes. The methodology involves six critical success factors including shared change purpose, effective change leadership, powerful engagement processes, and sustained commitment. Changefirst trains over 12,000 people annually and provides tools and resources to close the "value gap" often seen between planned benefits and actual benefits realized in change initiatives.
Managing and improving operational delivery - National Audit Office process m...UK National Audit Office
This document discusses the National Audit Office's (NAO) work in assessing operational delivery and process management maturity across UK government organizations. The NAO has developed a Process Management Maturity Analytic tool consisting of 40 questions across 5 areas to evaluate how well organizations manage business operations. The NAO has found that UK government organizations are generally least mature in areas like understanding customer demand and empowering staff to continuously improve. Moving forward, the NAO aims to help close these performance gaps and share best practices both within the UK government and internationally.
The document discusses key principles of an Agile vision and body, including:
- The brain of Agile focuses on leadership, self-organization, and developing an Agile mindset.
- The heart emphasizes using short time boxes for iterations, releases, meetings and other activities.
- The legs represent running lean by using minimum viable products, pivoting when needed, and eliminating waste.
- The senses refer to the importance of measuring to improve.
- The family represents scaling Agile through teams using Agile release trains.
- Protection involves managing risks through practices like estimation, complexity analysis, and change management.
Prime Sales Solutions Success Achiever Overview Power Point 2010Matt Zimmerman
The Success Achiever program is a results-driven set of methodologies developed by Business Solutions experts to successfully evaluate, deploying and maintain business solutions, one step at a time. This methodology is derived from more than a decade of best practices, positions and focuses your organization to realize a clear and defined set of goals. The end results are realistic benchmarks and exceptions while achieving a rapid return on investmen
Agile Developers Create Their Own Identity[1]Surajit Bhuyan
The document discusses building an organizational culture of agility rather than just following Agile practices. It lists agility services like software craftsmanship and agile coaching. It also discusses assessing and improving team agility through methods like retrospectives. Overall the document emphasizes focusing on agility at both the team and organizational level.
Agile Improvement Method - Andrew Griffits (Lamri)Paula Gomes
The document discusses an agile improvement method for process improvement projects. It summarizes that traditional improvement projects often fail to meet the needs of agile teams. It then proposes adapting agile principles to improvement projects, such as focusing on rapidly delivering useful improvements, deploying improvements frequently in small batches rather than large projects, and using face-to-face communication. The presentation then outlines how an agile improvement method may look by dividing it into initiation, mobilization, and delivery phases with examples of activities for each phase like understanding needs, prioritizing improvements, and packaging improvements to address specific pain points or deliver outcomes.
- 91% of theatres actively use Facebook with a median number of 1,238 fans per theatre. More frequent posting on Facebook leads to more fans and user engagement. Only 37% of theatres link to their Facebook page from their homepage.
- 73% of theatres are on Twitter with a median number of 77 followers per theatre. 1/3 of theatres tweet daily. Case study of ART found that tweeting more frequently leads to more people tweeting about or to that theatre.
- Check-ins on foursquare for theatres has grown significantly since 2010, though levels of user engagement have remained relatively flat. Early adopter theatres have more check-ins on average.
Chorus america social media step by stepDevon Smith
Chorus America 2011pre- conference seminar. Social Media Step by Step (for beginners). Creating a social media strategic plan, Facebook, Twitter, YouTube, Tools to monitor & measure social media.
Agile Developers Create Their Own IdentityAjay Danait
The document discusses building an agile organization culture and delivering agility through team agility. It focuses on agility assessment, coaching teams in agile practices like Scrum and XP, and transforming the organization. Specific services mentioned include software craftsmanship, agility in maintenance, agile enterprise architecture, and agility nurseries. The document also discusses assessing and improving team agility through techniques like value stream mapping and team chartering.
This document discusses key concepts in food and beverage management. It defines management as the process of planning, organizing, coordinating, staffing, directing, controlling, and evaluating. The management process aims to achieve organizational objectives through allocating resources and solving problems. Several management tasks are also outlined, including defining goals and objectives, developing action plans, organizing work assignments, effective communication, delegation, scheduling, recruiting and hiring, measuring performance, and assessing training programs. Daily activities for managers are listed such as developing budgets, addressing problems, coordinating special events, revising job descriptions, supervising employees, controlling costs, and conducting performance reviews. Managers must work with both primary and secondary groups to provide hospitality to guests.
The document discusses how companies can embrace change and drive innovation through software. It outlines a 4-phase framework for continuous process improvement using IBM Rational tools. Phase 1 involves establishing business objectives. Phase 2 prioritizes practices and defines an improvement roadmap. Phase 3 accelerates adoption with tools to improve requirements management, architecture, and development alignment. Phase 4 reports on results to identify further improvements. The framework aims to help companies optimize resources, deliver smarter products, and improve profits through incremental capability advances.
Normalizing agile and lean product development and aimRussell Pannone
The what, why, and how of agile and lean product (system-software) development and delivery is not one persons vision alone; to become reality it needs to be a "shared" vision through negotiation and compromise between individuals, the team and the organization.
The following is a set of norms for your agile and lean product (system-software) development teams to rally around and evolve.
1. The document discusses a case where an IT implementation project at a call center was facing challenges with select employee groups due to a lack of understanding of individual traits and how they impact change tolerance.
2. It introduces the concept of a "Worker's Microcosm" framework to gain a holistic understanding of workers' profiles, performance drivers, interests and how they align with job design and corporate systems before implementing changes.
3. Applying this framework through behavioral assessment tools during an ERP integration project helped identify the most compatible workers for specific process roles, improving performance synergy and project success.
The document provides an overview of Gemini Consulting's approach to leading organizational change. It discusses how the business environment is changing and requiring different approaches to change. Gemini's approach is grounded in tools developed from behavioral change insights that focus on changing individual behaviors through small groups. Gemini interventions create joint project teams of clients and consultants to serve as a safe environment to experiment with new ways of working and accelerate change. Gemini is evolving its approach to address continuous change and spreading learnings throughout organizations.
Agile2011 - What do we supposed to do with these managers now?skipangel
This document discusses the role of managers in agile organizations and options for how managers can adapt to agile ways of working. It suggests that managers transition from being directive leaders to being catalyst leaders who facilitate teams and create collaborative environments. Some ways managers can support teams mentioned are by reducing dependencies between teams, reducing technical and other debts, minimizing waste, and investing in learning. The document also notes that for agile to be successful, the entire organization needs to understand strategy, have a learning culture instead of a culture of fear, and optimize outcomes for the whole system rather than individual parts. It acknowledges that agile cannot address all challenges and is a significant organizational change and journey rather than a destination. Strong leadership is needed to make the
Refactoring the Organization Design (LESS2010)Ken Power
These are the presentation slides from a presentation I gave at the Lean Enterprise Software and Systems Conference 2010 (LESS 2010, http://less2010.leanssc.org/). The presentation is based around the paper I submitted that is published in the proceedings.
From the paper abstract:
Every organization has a design. As an organization grows, that design evolves. A decision to embrace agile and lean methods can expose weaknesses in the design. The concept of refactoring as applied to software design helps to improve the overall structure of the product or system. Principles of refactoring can also be applied to organization design. As with software design, the design of our organization can benefit from deliberate improvement efforts, but those efforts must have a purpose, and must serve the broad community of stakeholders that affect, or are affected by, the organization. Refactoring to agile and lean organizations demands that we have a shared vision of what the refactoring needs to achieve, and that we optimize the organization around the people doing the work.
The document discusses radical redesign in public services and caring roles. It explores moving from incremental to radical innovation by improving current services compared to mobilizing community resources and changing outcomes. Diagrams show moving from inside to outside the system and changing goals rather than means. The design process involves learning from users, generating ideas through co-design, and creating solutions that shift behaviors.
The document discusses group problem solving and facilitation. It describes the problem solving/team building (PS/TB) approach, which is an iterative, participative process that gets results by solving problems. The PS/TB approach involves 7 steps: 1) headlining the problem, 2) providing background, 3) generating ideas, 4) selecting ideas, 5) getting benefits and concerns, 6) working critical concerns, and 7) getting an action plan and next steps. The document also discusses effective facilitation skills and the role of the facilitator in leading a group through the problem solving process.
This document discusses the experience of a team at Huawei Technologies India in adopting Theory of Constraints (TOC) and Kanban practices. The team analyzed constraints through TOC to identify gaps like inefficient processes and lack of resources. They developed a future state tree to break conflicts with win-win solutions. This led them to adopt agile development using Scrum and share team members across components. Further TOC analysis identified challenges of reduced testing time and high workload bursts. The team addressed this by prioritizing work daily in one piece flow and using Kanban to control queues and delays. This improved efficiency by ensuring continuity of workflow.
This document summarizes an organization called Changefirst that provides change management consulting and training. It discusses Changefirst's People Centred Implementation methodology for helping organizations implement projects effectively by engaging people and building skills to adapt to changes. The methodology involves six critical success factors including shared change purpose, effective change leadership, powerful engagement processes, and sustained commitment. Changefirst trains over 12,000 people annually and provides tools and resources to close the "value gap" often seen between planned benefits and actual benefits realized in change initiatives.
Managing and improving operational delivery - National Audit Office process m...UK National Audit Office
This document discusses the National Audit Office's (NAO) work in assessing operational delivery and process management maturity across UK government organizations. The NAO has developed a Process Management Maturity Analytic tool consisting of 40 questions across 5 areas to evaluate how well organizations manage business operations. The NAO has found that UK government organizations are generally least mature in areas like understanding customer demand and empowering staff to continuously improve. Moving forward, the NAO aims to help close these performance gaps and share best practices both within the UK government and internationally.
The document discusses key principles of an Agile vision and body, including:
- The brain of Agile focuses on leadership, self-organization, and developing an Agile mindset.
- The heart emphasizes using short time boxes for iterations, releases, meetings and other activities.
- The legs represent running lean by using minimum viable products, pivoting when needed, and eliminating waste.
- The senses refer to the importance of measuring to improve.
- The family represents scaling Agile through teams using Agile release trains.
- Protection involves managing risks through practices like estimation, complexity analysis, and change management.
Prime Sales Solutions Success Achiever Overview Power Point 2010Matt Zimmerman
The Success Achiever program is a results-driven set of methodologies developed by Business Solutions experts to successfully evaluate, deploying and maintain business solutions, one step at a time. This methodology is derived from more than a decade of best practices, positions and focuses your organization to realize a clear and defined set of goals. The end results are realistic benchmarks and exceptions while achieving a rapid return on investmen
Agile Developers Create Their Own Identity[1]Surajit Bhuyan
The document discusses building an organizational culture of agility rather than just following Agile practices. It lists agility services like software craftsmanship and agile coaching. It also discusses assessing and improving team agility through methods like retrospectives. Overall the document emphasizes focusing on agility at both the team and organizational level.
Agile Improvement Method - Andrew Griffits (Lamri)Paula Gomes
The document discusses an agile improvement method for process improvement projects. It summarizes that traditional improvement projects often fail to meet the needs of agile teams. It then proposes adapting agile principles to improvement projects, such as focusing on rapidly delivering useful improvements, deploying improvements frequently in small batches rather than large projects, and using face-to-face communication. The presentation then outlines how an agile improvement method may look by dividing it into initiation, mobilization, and delivery phases with examples of activities for each phase like understanding needs, prioritizing improvements, and packaging improvements to address specific pain points or deliver outcomes.
- 91% of theatres actively use Facebook with a median number of 1,238 fans per theatre. More frequent posting on Facebook leads to more fans and user engagement. Only 37% of theatres link to their Facebook page from their homepage.
- 73% of theatres are on Twitter with a median number of 77 followers per theatre. 1/3 of theatres tweet daily. Case study of ART found that tweeting more frequently leads to more people tweeting about or to that theatre.
- Check-ins on foursquare for theatres has grown significantly since 2010, though levels of user engagement have remained relatively flat. Early adopter theatres have more check-ins on average.
Chorus america social media step by stepDevon Smith
Chorus America 2011pre- conference seminar. Social Media Step by Step (for beginners). Creating a social media strategic plan, Facebook, Twitter, YouTube, Tools to monitor & measure social media.
The document outlines an agenda for a social media masterclass on mechanics of measurement to be held on April 18, 2011 in San Francisco. The agenda includes sessions on strategy, Google Analytics, Facebook Insights, Twitter tracking, blog tracking and other platforms. It also allocates time for Q&A. The document provides guidance on key metrics to measure across various social media platforms, how to interpret data from tools like Google Analytics and Facebook Insights, and how to structure experiments and analyze results.
This little guide helps those managing, creating, delivering or evaluating training and instruction. It can also make a great "brief" for those thus engaged to share with their program managers, directors, leaders, etc. so they can understand WHY you do what you do and WHY you are asking for the kinds of support you are.
Digital Media Assessment for BACTheatre provides recommendations across several social media platforms:
1) It recommends increasing activity and engagement on Facebook, Twitter, YouTube, Flickr, Foursquare, Yelp and blogging platforms based on metrics of peer theater organizations.
2) It highlights specific organizations to learn from that are performing well across different social media platforms.
3) It provides screenshots and calls out specific actions BACTheatre can take to improve their profiles, increase followers, drive more traffic and engagement for things like custom URLs, adding images/bios, seeding discussion topics, claiming venues and reaching out within the community.
The document analyzes data from 73 LORT theaters' use of Facebook. On average, theaters post about once per day, generating 2-3 comments per post. Fewer than half raise money or review engagement. The document develops indexes to measure and compare theaters' efforts, impacts, and return on investment of their Facebook activities. It finds some theaters achieved higher impacts relative to efforts, while others exerted more effort with less impact than peers.
NEA Bright Spots and Blank Spots: How the Arts are Using Digital in 2014Devon Smith
This document discusses how the arts are using digital technologies and outlines several areas of focus including online media and publications, digital agencies and support organizations, meetups and conferences, online appearances, hardware and software, social media as art, technology partnerships, advocacy campaigns, data collection and analysis, and persuasive online content. It poses questions about each area and how they relate to advancing arts initiatives using new technologies.
Management Training requires Assessment and Analysis which is explained in Effective HR. This presentation explains the significance of ‘needs analyses’ in training. Understand various types of training needs and the processes involved in Training Analysis, know the components of a training Needs Assessment and the methods for collecting data.
For more such innovative content on management studies, join WeSchool PGDM-DLP Program: http://bit.ly/SlideShareEffectHR
Join us on Facebook: http://www.facebook.com/welearnindia
Follow us on Twitter: https://twitter.com/WeLearnIndia
Read our latest blog at: http://welearnindia.wordpress.com
Subscribe to our Slideshare Channel: http://www.slideshare.net/welingkarDLP
This document discusses motivation in the workplace. It covers:
1. Why motivation matters for business performance and profitability.
2. How understanding employee psychology, fairness, and engagement can help motivate staff.
3. The Team Action Management process that some companies use to gather anonymous staff feedback and develop projects to address issues in a way that promotes fairness and motivation.
Do annual performance reviews help mission-driven organizations succeed or are they just another administrative function that takes time away from more important things? We believe that a well designed system can provide positive feedback to employees helping them do a better job and create a stronger organization. But doing so in the proper setting, context, and manner is critical to carrying out successful performance reviews. We'll show you how during this 60-minute design strategy workshop.
PCV2013 The Leadership Role for Product ManagersDerek Pettingale
This session will review leadership dynamics and the cross-functional leadership required to propel your product to a greater level of success. Includes Additional Slides on: Leadership Qualities, Organizational Culture Grid, Matrix of Requirements for Effective Change, Team Work Values and Manifesto.
This document discusses coaching an organization through an agile transformation. It covers preparing for change, establishing an enablement team to guide the transformation, choosing pilot teams, overcoming challenges like changing leadership styles and organizational structures, and monitoring progress through metrics. The transformation impacts how work gets done, leadership approaches, and the culture. With the right preparation and coaching, organizations can develop the agility to sense and respond to changing needs.
The document outlines 5 steps to define a team's structure and build interaction by identifying the team and roles, establishing metrics for success, clarifying responsibilities, defining processes, and addressing interpersonal dynamics. It also recommends practicing devil's advocacy to develop contingency thinking by collaboratively identifying what could go wrong and ensuring rapid response to unexpected events. The overall objectives are to use the 5 steps to structure the team and build interaction, and develop contingency thinking through devil's advocacy.
Linda Dulye IABC 2010 Global Conference PresentationDulye
Managers play a key role in organizational performance and employee productivity. This document outlines techniques for establishing a "Spectator-Free Workplace" where managers are actively communicating and engaging with employees. It provides tools and best practices for coaching managers to be better communicators, including establishing clear communication standards, leveraging multiple channels, providing context, soliciting feedback, and continuously measuring effectiveness. Regular calibration activities like informal polling, feedback forms, and data debriefs can help ensure managers are held accountable for their communication responsibilities.
The document summarizes an assessment center skills session that covered:
1) The current graduate job market which is very competitive with many graduates and few jobs.
2) The different activities commonly used at assessment centers like interviews, group exercises, presentations, and case studies. Employers use these to evaluate skills, behaviors, and suitability for the role.
3) Strategies for success at assessment centers, focusing on interviews and group tasks. Participants learned how to prepare, practice, and perform well during activities by demonstrating key competencies and working effectively with others.
Infinity Learning Systems provides training and development programs to help organizations build effective teams, engage employees, and optimize productivity. Their core purpose is "Building competencies with fun" through competency-based, experiential training delivered in an inspiring, educating, and entertaining way. Standard programs cover topics like communication, leadership, performance enhancement, and stress management, while customized programs are tailored to specific learning objectives.
The document discusses teams and what makes an effective team. It defines a team as a group of interdependent people committed to a shared goal, with clear roles and accountability. Teams are important because tasks have become more complicated and require diverse expertise. The document then outlines Tuckman's model of team development, including the forming, storming, norming, and performing stages. It also lists six "sins" that can undermine team building and keys to building great teams, such as commitment, contribution, communication, and conflict management. Finally, it provides measures of highly effective teams, including being customer-focused, transparent, incubators of leaders, and value-adders.
This document provides an overview of ISO 9001 and the process for obtaining ISO 9001 certification. It discusses what ISO is, the advantages of certification including increased profitability, risk management, and customer trust. It outlines the steps to achieve certification including gaining management commitment, defining processes, identifying job skills, monitoring performance, and continual improvement. It recommends starting the certification process immediately by developing internal resources or engaging an external consultant.
This document provides an overview of ISO 9001 and the process for obtaining ISO 9001 certification. It discusses what ISO is, the advantages of certification including increased profitability, risk management, and customer trust. It outlines the steps to achieve certification including gaining management commitment, defining processes, identifying job skills, monitoring performance, and continual improvement. It recommends starting the certification process immediately by developing internal resources or engaging an external consultant.
This document provides an overview of ISO 9001 and the process for obtaining ISO 9001 certification. It discusses what ISO is, the advantages of certification including increased profitability, risk management, and customer trust. It outlines the steps to achieve certification including gaining management commitment, defining processes, identifying job skills, monitoring performance, and continual improvement. It recommends starting the certification process immediately by developing internal resources or engaging an external consultant.
This document discusses the concept of "Lean Security", which aims to transform organizational culture and behaviors to better align security initiatives with business goals. It argues that security initiatives often fail because the business is misaligned and incentives are broken. Lean Security applies principles from Lean and DevOps to reform culture and priorities, treating security as an emergent property. The goal is to create a "generative culture" with cooperation, learning and shared values.
This document outlines an integration plan to assess an organization's structure, competencies, and processes. It involves:
1) Conducting an assessment of the organization, roles/responsibilities, communication relationships, and systems/processes.
2) Identifying strengths, weaknesses, opportunities, and threats through interviews, benchmarking, and analyzing customer requirements.
3) Developing action plans to address gaps, including reviewing competencies needed and ensuring functions are best-in-class.
The goal is to identify improvements to make sales, marketing, supply chain, and other functions work more effectively together.
Competency romance pt1 Cooper-Thomas ~ The promise of the competency appro...Frank O'Connor
The document discusses the promise of the competency approach for improving performance. It outlines three origins of competencies - vocational/educational, behavioral, and strategic. Competencies are purported to improve recruitment, performance management, career development, and organizational strategy. However, competencies also carry risks such as issues validating competency criteria and reducing employee flexibility. While competencies are increasingly adopted in practice, more empirical research is still needed to determine if they truly fulfill their promise to improve organizational and individual performance.
Identifying and Managing Waste in Complex Product Development EnvironmentsKen Power
Product Development can be viewed as a Complex Adaptive System. Different people, groups, organizations and systems collaborate in a complex network of relationships and dependencies to produce something of value - generally a product or service. Identifying waste in this value network is a critical step towards creating a truly lean organization.
These slides are from an interactive, hands-on workshop that I ran at the Agile India 2012 conference in Bengaluru, India.
There is a corresponding Blog entry here:
http://wp.me/pSOIL-fE
The document discusses performance consulting, which seeks to develop holistic strategies to improve performance through changes in measurement, education, staffing, and tools. Performance consulting can be divided into organizational development, professional development, and personal coaching. It is needed due to challenges like globalization and rapid change that demand broader skills from managers, leaders, and workers. As a result, human resources staff must become performance consultants who improve individual, team, departmental, and organizational performance through expertise, tools, and skills. The role of consultants is to partner with clients to define needs, develop responses, and implement and measure actions for performance improvement.
Agile Lessons Learned From the TrenchesBrendan Flynn
Brendan Flynn presented on lessons learned from implementing Agile practices at Pointroll. Key lessons included: creating visibility into development processes and metrics; gaining executive support; making data-driven decisions; focusing on business value over features; ensuring proper training; optimizing across teams; and rigorously inspecting and adapting practices over time. While hard work, adopting Agile frameworks improved delivery, quality, and alignment between business and technology teams at Pointroll.
The document discusses teams and work groups. It defines teams as formal groups that work together to achieve common goals, with more cohesiveness than individuals. Benefits of teams include increased innovation, higher quality decisions, improved processes and communication, and reduced turnover. However, teams also face limitations such as groupthink, social loafing, and diversity challenges. Different types of teams are described such as cross-functional, self-managed, and task force teams. The stages of team development - forming, storming, norming, performing, and adjourning - are outlined. Features of high-performance teams and tips for effective teams are also provided.
Performance management skills for managersMeera Goyal
This document outlines the agenda and key topics covered in a training course on performance management skills for managers. The course will address both dealing with poor performance and helping good performers excel. It will cover understanding performance cultures, preempting issues, communication skills, motivation, applying principles to teams, the manager's role in maintaining performance, and turning good performers into great ones. Participants will engage in exercises applying the concepts to practical scenarios and discussions.
2. What IS Excellence?
Burning Platform Compelling Destination
Increased competition Safe, productive, efficient
Increased regulatory workplace
oversight Value Adding work for
Demanding Customers customer
Supplier of Choice
Costs
Employer of Choice
3. “Eye Diseases”
Nearsighted
Farsighted
Blind
Stigmatism
Poor Peripheral
“Floating spots”
What keeps YOU from seeing?
4. The Four “P’s” of Excellence
1. Paradigms – Mindset, attitudes, mental
models, assumptions and “rules”
2. People – individuals, workgroups & teams
3. Process – simplified & standardized
4. Problem-Solving – disciplined & structured
5. Seven Key
Improvement Paradigms
1. Quality/Value is defined by the Customer
2. Focus on Better not Best! (Kaizen)
3. People REALLY are the key
4. Understanding Process as Key to World
Class
5. Systems Thinking (Whole and Parts)
6. Horizontal Structure (end to end process)
7. Teams as the “fuel” for success
6. Paradigm 1 - Quality
THINGS THE CUSTOMER IS
LOOKING FOR …
Quality is meeting or exceeding PRODUCT
the requirements of the Performance
Features
customer Conformance
Quality (right thing/right way) Timeliness
Serviceability
actually costs less Durability
Aesthetics
Present/Pass performance is no Reputation
guarantee of future success
SERVICE
Quality is an ever-rising bar Reliability
Remember the 1-10-100 Rule! Responsiveness
Competence
Access
Courtesy
Communication
Security
Understanding
“Tangibles”
7. Paradigm 2 – Focus on Getting
BETTER
Continuous – every day, effort, task, person
Kaizan – incremental improvement
Competing against YOURSELF
Listen to Voice of the Customer, Your Process, Your
Team
Achieved through disciplined application of
following:
LEAN – reduce waste/increase value
DMAIC – reduce variation/improve process
Operational Excellence – planned, predictable
performance
8. Paradigm 3 – People ARE Key
To engage yourself and your team, think
P.R.I.D.E!
Purpose – focus on what is important/alignment
Recognition – reward behaviors you want –
team based
Involvement – no “opting out” – engagement –
everyone together!
Development – depth/breadth of
skills/growth/”Bold Moves”
Empowerment – ownership, decision, action,
accountability
9. Paradigm 4 – Process Focus
Well-defined and documented:
SIPOC (Supplier, Input, Process, Output, Customer)
Process Flow Diagram/VSM
RACI (roles and responsibilities)
Service Level Agreements
Performance Measures
Other Policy/Guidance documentation
Gap Analysis/Desired State/”Closure Plan”
Define/Measure/Stabilize/Control/Improve
End-to-End view (touchpoints and handoffs)
Planned, consistent feedback and
communication that is constantly improved
10. Paradigm 5 – Systems Thinking
Thinking in terms of the Whole v.s. Parts
Making the routine “routine”
No heroics – no need for “knights on white
horses” or “firefighters”
Supportive Behaviors – walking the talk!
Integration of People, Process, and
Technology
Think GLOBAL, act LOCAL
11. Paradigm 6 – Horizontal Structure
Seamless internal execution from Supplier all
the way through to the Customer
Feedback loops to enable continuous “real time”
communication (VISIBILITY!)
Series of processes involving multiple teams,
functions, and departments (Core, Support,
Enabling)
Developing strong customer-supplier
relationships between EVERY team involved in
a work process
12. Paradigm 7 - Teams
Teams own parts of the whole process
Teams measure their own performance
Teams improve their part of the process
Teams exist to add value to the product or
service received by the customer
Characteristics of an effective team:
Common goal
Common identity
Common language/tools/procedures
Common work space/environment
13. The Perfect Employee?
Behaviors:
What do they say?
What do they DO?
Keys to Developing/Keeping:
Role Clarity – Do they know what to do?
Ability – Can they do it/have resources?
Willingness – Do they want to?
Leadership – self/team/formal &
informal/relationship
Effective Change Management
14. Process As Key
Supplier Keys to Effectiveness
Input Well defined
Requirements Well documented
Your Value-Adding Used Measured
Work continuously
Outputs Constantly Improved
Requirements Visible, Open Book
Customers
Critical to Quality
(CTQs)
Plan your work, work your plan, Continuously improve!
15. Systems Thinking
LEVELS FOCUS & READINESS
Cell Self
Organ One to one
Organism/Individual Work teams
Group/Team Between Departments
Organization Total organization
Society/Community Organization out to its
Nations/Global environment (business,
social, governmental,
other)
There are NO “closed”
systems
16. Process View of the Organization
Company
Function A Function B Function C
Management/Guiding Process
requests
Core Process
Customers
Sub-Core Process
Support/Enabling Process
Resources
Support/Enabling Process
17. Teams as a System
Traits of Effective Barriers to
Teams Effectiveness
Trust Unclear goals/mission
Mutual Support Formal, tense meetings
Communication Talk, no communication
Team goals/objectives Formal decisions only
Conflict resolution Lack of cooperation
Full utilization of inside and outside
members No self-assessment
Accountability No results/missed goals
Open climate
18. Teams as a System
Stages of Growth Dealing with Change
FORM – why we here? N+1, N-1
STORM – who does what? End, Transition, Begin
NORM – how we agree to Cycle:
work together Deny
PERFORM – getting it done! Resist
ADJOURN – moving on & Explore
celebrating our success and Accept
learning Commit
19. Teams as a System
Communication Conflict Resolution
Continuous Conflict is normal, natural,
Common and – if handled properly –
Consistent healthy for
Push/Pull teams/individuals
Visual/Verbal/Vocal State your case
Feedback! Listen to the other
Groundrules person’s side
9 Behaviors Ask for and negotiate
Agenda/Action Plans new behaviors and
resolutions
REMEMBER: When meeting as a team, there are No “Pink
Elephants!” (i.e. topics you cannot discuss)
20. Problem Solving
Steps in… Effective Problem-
Identify the issue (pain Solving Requires…
or gain) Patience
Define the problem Discipline
Identify suspected Creativity
causes Repetition
Verify most likely Honesty
Identify possible Facts/Data/Information
solutions Cause & Effect
Develop an Action Continuous Learning
Plan to test your Courage!
solutions
Evaluation your action
plan
21. Problem Solving
Some of the LEAN/DMAIC/OE Tools…
Brainstorming
Visual Mapping (PFD, MindMap, C&E)
Prioritizing (Pareto/Rubric/Decision Matrix)
Interpreting (Control Charts, Scatter Diagram)
DMAIC – Define, Measure, Analyze, Improve,
Control
LEAN – Value, Waste, 5 S, Mistake Proofing
Process Performance Measurement
22. Problem Solving
Decision Making
Asking the right Questions (5WH) (5 Whys)
Establishing evaluation Criteria (Better, Faster,
Cheaper?)
Conducting the Analysis (Cost, Risk, Resources,
Impact)
Identifying/Prioritizing Alternatives (SMART, short
term, long term)
Making the Decision (Type, acceptability, support)
Executing (fast and flawless!)
Evaluating (how’d we do?)
Improving (NEXT time, we will…)
23. Skills to Improve Problem Solving
Continuous Learning (mistakes AND good)
Competency in the work/process and OE tools
Communication – up/down/across/outward
Self-management – understanding bias, culture,
politics
Adaptability and Flexibility – individual and team!
Team dynamics/cohesion – “It takes a village!”
Influence and leadership – getting/using/improving
Continuous assessment of self/team (lessons,
success)
24. Just DO IT!!!
Project/Problem Selection…
Pick something that everyone can agree needs
to be fixed, prevented, or improved
Make it meaningful and relevant to real
issues/real world!
Use your data – focus on impact if improved
Be realistic – SMART goal it
Fruit: on the ground, low hanging, middle, top
of the tree
Don’t Miss the Obvious! AND…Don’t be
afraid to ask for some help in “harvesting”
your fruit!