Академический Документы
Профессиональный Документы
Культура Документы
PROJECT LEADERSHIP
Lessons from 40 PPM Experts on Making the Transition
from Project Management to Project Leadership
Sponsored by:
2
Foreword............................................................................................3
Introduction......................................................................................4
Our Project Leadership Experts...................................................5
Learning to Share................................................................................9
Nurturing Effective Communication............................................10
Leading from the Front................................................................12
Project Leadership, Not Project Management.............................13
Building Trust One Project at a Time...............................................14
The Keys to Success: Ownership, Transparency, and
Accountability.....................................................................................15
Nailing the Vision: Ensuring Project Success Through
Clarity....................................................................................................17
Business-focused Leadership........................................................18
Wild Dogs and PMs: Team Building for Successful Projects.............19
Preparation, Visibility, Empowerment..........................................20
Communicating with Empathy........................................................21
Going from Boss to Teammate..................................................22
The Deal is in the Details.................................................................24
Virtual Leadership.............................................................................25
How WIFM Rescued a Failing Project.........................................26
Winning Stakeholder Support....................................................27
Lightening the Weight of the World Through Trust.................28
Moving Projects Beyond Analysis Paralysis.............................29
Getting Down to Genuine Leadeship..........................................31
TABLE OF CONTENTS
No More Winging It: Devising a Plan to Save a Project........32
Trust and Respect: The Keys to Successful Projects...............33
Risking Your Popularity to Be a Strong Leader.........................34
Connecting Sustainability to the Enterprise..............................36
Committing to an Agile Transformation.....................................38
Encourage Autonomy, Collaboration, Exploration...............39
Rescuing Failing Projects............................................................40
Trust: The Key to Successful Leadership...................................42
Becoming the Linchpin for Your Project.......................................43
Implementing Situational Adapted Leadership.......................44
Changing an Organizations DNA.................................................46
Ensuring Success Through Face-to-Face
Communication................................................................................47
Leading Those Who Follow...........................................................48
Starting Projects with Love and Integrity..................................49
Cultural Competence: Effective Leadership in
Multicultural Environments...........................................................50
Project Leadership: The Main Ingredient in Getting
Troubled Projects Back on Track.................................................52
Delegating Your Way to Project Leadership.............................53
Consistent Project Management Without Excuses ...............54
Clear Communication Leads to Commitment.........................56
Principles of Performance-Based Project Management.......57
Love Your Project, and Your Team Will, Too.............................59
Meet AtTask...................................................................................60
3
FOREWORD
S
trong project leadership can make the diference between success and failure but is surprisingly elusive to many
businesses.
When it comes to project management, we tend to talk about the tacticalthe assignments, the tasks, the approvals, and
so on. But business is evolving, and many project teams are now being asked to lead change, instead of just timelines
and milestones. This evolution is accelerating and is driven by fresh thinking and business necessity supported by
advanced technologies that are highly accessible to a much broader range of contributors. Efectively managing work is
no longer just the role of a few specialists.
At AtTask, weve been both witnessing and enabling this trend for many years. Its the reason our strategic focus goes
beyond helping clients better manage projects. Our Enterprise Work Management solution allows them to view work in a
holistic wayproviding complete visibility across not just projects, but the entire lifecycle of work.
With visibility comes transparency, confidence, and ultimately, the power to lead. Decisions no longer need to be made
with out-of-date and incomplete information, resources can be truly optimized, and productivity materially improved.
We hope youll fnd the collective wisdom captured in this eBook to be a source of insight and best practice as you
continue your own journey to be a project leader.
ERIC MORGAN
AtTask CEO
4
Gartner predicted a massive sea change in the world of project managementa change that is forcing project managers into
a greater leadership role and requiring them to work closely with senior executives. With the generous support of AtTask, we
reached out to 40 top Project and Portfolio Management (PPM) professionals and asked them the following question:
Please share a remarkable leadership secret that had a major impact on an enterprise
project you have managed. Please tell the story and the results that you achieved.
We received a range of insightful answers that paint a picture of an industry in transition. The essays in this book roughly
break down into three categories. Several of the practitioners focused on the new relationship that project leaders need
to forge with senior management, how to understand their concerns and communicate with them in any way that
works. Many PPM experts wrote about leading change and getting teams to work together in new ways. Finally, many of
our experts wrote about specific leadership techniques that have helped them clear hurdles and remove obstacles.
Making the shift from project management to project leadership isnt easy, but the rewards can be signifcant. We hope
the collective wisdom and hard-learned lessons contained in these pages will inspire you and help you take your own
teams to a higher level.
All the best,
DAVID ROGELBERG
Editor
2014 Studio B Productions, Inc. I 62 Nassau Drive I Great Neck, NY 11021 I 516 360 2622 I www.studiob.com
INTRODUCTION
5
Cesar Abeid
PROjECT MANAGER
Glen B. Alleman
PRINCIPLE
Paul Cable
CONSULTANT PROjECT
MANAGER
Naomi Caietti
PROjECT MANAGER /
CONSULTANT
Geof Crane
DOCTORAL STUDENT,
PROFESSOR & COACh
Michiko Diby
CEO
Michel Dion
PROjECT MANAGER
Deanne Earle
COMPANY DIRECTOR &
PROjECT CONSULTANT
Chris Field
GLOBAL PMO MANAGER
jef Furman
PROjECT MANAGEMENT
INSTRUCTOR / PM BOOk AUThOR
OUR PROjECT LEADERShIP ExPERTS
Frank Grippo
DIRECTOR OF WEB SERvICES
Bob Hartman
CERTIFIED SCRUM TRAINER
Barry Hodge
PROjECT MANAGER
Jon Hyde
PROGRAMME MANAGER
Michael Kaplan
FOUNDER AND CEO
Robert Kelly
MANAGING PARTNER
Torsten Koerting
MANAGING PARTNER
Susanne Madsen
PROjECT LEADERShIP COACh
Rich Maltzman &
Dave Shirley
CO-FOUNDERS
Margaret Meloni
PRESIDENT
Jose Moro
CEO
Carlos j. Pampliega
ARChITECT & PROjECT
MANAGER
Rob Prinzo
PRESIDENT
Patrick Richard
SENIOR PROjECT /
PROGRAM MANAGER
Gregg D. Richie
INSTRUCTOR
Ivn Carlos Rivera
Gonzlez
SR. PROjECT MANAGER
Tres Roeder
PRESIDENT
Johanna Rothman
PRESIDENT
Peter Saddington
PRINCIPAL
Susan de Sousa
DIRECTOR
Pam Stanton
AUTHOR, SPEAKER &
CONSULTANT
Stephanie Stewart
DIRECTOR OF AGILE LEADERShIP
Jo Ann Sweeney
FOUNDER
Peter Taylor
OWNER / DIRECTOR
Tony Toglia
DIRECTOR, PROjECT
MANAGEMENT OFFICE
Ricardo Viana Vargas
DIRECTOR - PROjECT
MANAGEMENT
Cinda voegtli
CEO
Ed Wallington
PROjECT MANAGEMENT
ADvOCATE
Neil Walker
PROGRAM & PROjECT
PRACTITIONER
Todd C. Williams
PRESIDENT
6
Share a
remarkable
leadership
secret that had
a major impact
on an enterprise
project you have
managed.
Many enterprises may have good data,
but because they are working in silos . . .
these data are not available to end users
when they require it.
Ed Wallington
When it comes to organizational project
management, communications is a critical
component that, when executed properly,
links all project stakeholders to a common
set of goals and actions.
Michael Kaplan
Project leadership relates to people,
relationships, and behaviors.
Neil Walker
7
Leadership is setting a new direction or vision for a group to follow, while
management is controlling resources in a group according to defned standards.
Peter Taylor
Swift trust occurs when a diverse group is brought together in a temporary
organization, such as a project ofce or virtual team created for an urgent project.
Naomi Caietti
I included stakeholders from all areas of the organization, not just IT and not just
the team members, which helped elevate stakeholder interest, bring transparency,
and break down silos, subsequently driving success.
Tony Toglia
8
I dont begin a project until I fully understand it. This means that I will sit with
project sponsors and not proceed until I have nailed down their vision.
Michiko Diby
What turned the project around was business-focused leadership by the sponsor
and PM as well as business-focused collaboration by the team to defne and pursue
what mattered most.
Cinda Voegtli
The role of the PM is frst and foremost to create an environment in which the PMs
team can be successfulnothing more, nothing less.
Chris Field
9
O
ne aspect that enables an enterprise to work efciently is the
ability to access up-to-date information in a timely manner.
Many enterprises may have good data, but because they are working
in silos (either because of structure or culture), these data are not
available to end users when they require it. There is a general recognition and
emphasis on creating a single source of the truth that staf and stakeholders
can access as appropriate. This requires an enterprise-wide change in working
practice and culturethe ability to share.
Enabling change on an enterprise scale requires buy-in from a wide range of
staf, from directors to operational delivery teams. The technical aspects of
this type of project are relatively well known, understood, and achievable; the
main efort is understanding and articulating the benefts and cultural change
required and making the change happen. The project manager (PM) in this
instance must not to only focus on the core project deliverablea system to
enable secure data storage and sharingbut also on the organizations buy-
in and implementation, which requires the ability to articulate the long-term
benefts (having a clear view on what success looks like) and using negotiation
and persuasion skills to make it happen at all levels of staf.
This type of project can easily lose steam without senior executive buy-in and
support. You will face a lot of push back when mobilizing cultural change, so
communication is key. A PM is conformable communicating at a project delivery
level, but this is not always the case when engaging senior executives. A diferent
tack is required, one focusing not on the technical detail but reinforcing why the
project is being done, what is required to efect change, and what the impact is
on the executives and their teams.
There is a need to personally tailor the benefts and impact to each executive
and explain it to them regularly. Go out on a limb, buy them a cofee, and have a
chat. Regular personal engagement is important and efective.
KEY LESSONS
1
2
3
TO WORK EFFICIENTLY, AN
ENTERPRISE MUST BE ABLE TO
ACCESS UP-TO-DATE INFORMA-
TION IN A TIMELY MANNER.
ENABLING CHANGE ON AN
ENTERPRISE SCALE REQUIRES
BUY-IN FROM A WIDE RANGE
OF STAFF.
THE PM MUST NOT ONLY
FOCUS ON THE CORE PROJECT
DELIVERABLE BUT ALSO ON THE
ORGANIZATIONS BUY-IN AND
IMPLEMENTATION.
Many enterprises
may have good data,
but because they are
working in silos . . .
these data are not
available to end users
when they require it.
ED WALLINGTON
Dr. Edward Wallington is an
advocate of professional
project management and
business analysis in the
geospatial and management
information sectors. Ed is
a versatile and enthusiastic
project manager who has
a deep interest and belief
in the transfer of project
management theory into
operational application. Ed is
a member of the Association
for Project Management (APM),
a committee member of the
APM Programme Management
Specialist Interest Group, and
actively contributes to the
project portfolio community.
LEARNING TO SHARE
Twitter I Website
Project Management
Advocate at
edwallington.com
10
W
hen it comes to organizational project management,
communications is a critical component that, when executed
properly, links all project stakeholders to a common set of goals and
actions. If project managers (PMs) do not efectively share these basic
components or team members dont understand them, expected outcomes are
jeopardized and project budgets become subject to unwanted risk.
A basic prerequisite for a smoothly functioning project team is efective
communications within the team and between the team and other project
stakeholders. One of the dangers of project management is the belief that all
communication links are operating efectively just because people are talking to one
another. One of the most common pitfalls of communication is the assumption that
because a message was sent, a message must have been received.
According to Project Management Institute, all aspects of project communications
can be challenging to projects, but the major areas of concern are:
The gap in comprehending the business benefts; and
The language used to communicate project information being frequently
ambiguous and favored with project management slang.
The responsibility for developing and nurturing real communication links belongs
to the PM. Understanding that the communication requirements of projects vary
greatly, the PM can focus on several areas to increase project communications:
Remain an efective communicator.
Be a communications expediter.
Encourage good communications across boundaries.
Leverage technology efectively.
Use a project website.
Run efective meetings.
KEY LESSONS
1
2
3
ENSURE COMMUNICATION
AMONG TEAM MEMBERS AND
BETWEEN THE TEAM AND
PROJECT STAKEHOLDERS.
CREATE AND USE A
COMMUNICATIONS
MANAGEMENT PLAN.
PLAN COMMUNICATION
INTERNAL AND EXTERNAL
TO THE PROJECT.
When it comes to
organizational project
management,
communications is
a critical component
that, when executed
properly, links all
project stakeholders to
a common set of goals
and actions.
MICHAEL KAPLAN
Michael Kaplan is the founder
of SoftPMO, a New Yorkbased
consulting frm that specializes
in improving execution and
resource management. He is a
recognized leader in program
management and serves as an
advisor and mentor to senior
executives. In more than 20
years of practice, Michael
has worked with several of
the worlds most successful
organizations, including
Fortune 500 companies and
government agencies, helping
them to achieve the full intent
of their most urgent and
critically important initiatives.
NURTURING EFFECTIVE COMMUNICATION
Founder and CEO of
SoftPMO
Twitter I Website I Blog
b
11
The key to communications starts with planning and includes:
Planning communication both external and internal to the project;
Identifying meetings, reporting, and announcements that will
occur with all stakeholders; and
Creating a communications management plan and using it.
Communications management must include planning and delivering information
related to the project to all project stakeholders, which includes the processes
needed to handle timely and appropriate collection, generation, dissemination,
and storage of project information and the defnition of critical links among
people, ideas, and information required for success.
KEY LESSONS
1
2
3
ENSURE COMMUNICATION
AMONG TEAM MEMBERS AND
BETWEEN THE TEAM AND
PROJECT STAKEHOLDERS.
CREATE AND USE A
COMMUNICATIONS
MANAGEMENT PLAN.
PLAN COMMUNICATION
INTERNAL AND EXTERNAL
TO THE PROJECT.
When it comes to
organizational project
management,
communications is
a critical component
that, when executed
properly, links all
project stakeholders to
a common set of goals
and actions.
MICHAEL KAPLAN
Michael Kaplan is the founder
of SoftPMO, a New Yorkbased
consulting frm that specializes
in improving execution and
resource management. He is a
recognized leader in program
management and serves as an
advisor and mentor to senior
executives. In more than 20
years of practice, Michael
has worked with several of
the worlds most successful
organizations, including
Fortune 500 companies and
government agencies, helping
them to achieve the full intent
of their most urgent and
critically important initiatives.
NURTURING EFFECTIVE COMMUNICATION
Founder and CEO of
SoftPMO
b
Twitter I Website I Blog
12
T
he perception of project managers (PMs) has changed
signifcantly over the past decade. I have witnessed a fundamental
shift in the sectors I operate inone that has seen a divergence from
the traditional PM role to encompass leadership qualities typically
reserved for executives.
Previously, PMs sat within an organizations command-and-control
management structure. This authoritarian approach was pervasive throughout
most sectors and typically limited fexibility, stifed innovation, and reduced
the ability to respond rapidly to issues. Marketplace changes over the past
decade have compelled senior executives to demand more from their people,
compelling their people to adapt swiftly to the onslaught of change through
extensive transformational change. PMs have been charged with unraveling the
plethora of business requirements to deliver projects successfully.
Senior executives set the strategic objectives of the organization, but they are
not experts on how the business runs at the operational level. The people
engaged at that level are. This disconnect is replicated at the project level, as
well. After all, no one person (or team) can do it all or know it all, and PMs are no
exception. A decade ago, I discovered that successful transformation projects
need efective actions by all of the people involved at every level. This certainly
requires greater levels of collaboration and infuence than hitherto seen, not only
within the delivery team implementing the change but across the organization
and even externally.
PMs face the challenge of gaining contributions and buy-in from people who dont
report directly to them. Therefore, project success often depends on ones ability
to infuence and persuade people at every level. This, in turn, requires leadership.
Project leadership relates to people, relationships, and behaviors. So, by leading
from the front, steering everyone toward a common objective, and engaging them
efectively en route, youll soon see enhanced project performance.
KEY LESSONS
1
2
3
COLLABORATION IS
ESSENTIAL TO SUCCESSFUL
TRANSFORMATION PROJECTS.
PROJECT SUCCESS OFTEN
DEPENDS ON YOUR ABILITY TO
INFLUENCE AND PERSUADE
PEOPLE AT EVERY LEVEL.
LEAD FROM THE FRONT.
Project leadership
relates to people,
relationships, and
behaviors.
NEIL WALKER
Neil Walker is a project
management professional,
consultant, and author. He has
more than 20 years of experience
leading and delivering technology-
enablement projects and business
transformation programs that
have aligned people, process,
and technology with business
strategy for blue-chip fnancial
services, professional services,
and Uk government organizations.
Neil has consulted across United
kingdom, Europe, Canada, and the
United States in specializations
such as program delivery
assurance, project turnaround,
strategic relationships, and
collaborative working.
LEADING FROM THE FRONT
Program & Project
Practitioner at Synatus
Twitter I Website I Blog
b
13
L
eadership has been described as the art of leading others to
deliberately create a result that wouldnt have happened otherwise.
This is something that happens every day in project management, yet
we call it just thatproject management rather than project leadership.
A confusing situation, but the diference can be thought of in the following
way: Leadership is setting a new direction or vision for a group to follow, while
management is controlling resources in a group according to defned standards.
Using this defnition, then, here is a great example of how such leadership brought
about a signifcant change. We had a project in which, despite good plans and great
people, we experienced issues resulting from the fact that neither we as the supplier
organization nor the customer had addressed the issue of organizational change
management (OCM) in any serious way. Yet, this was a big program of change running
over a planned period of two and a half years and afecting hundreds of people.
Recognizing this gap and the risk to the overall project, the customer project
manager and I agreed that we needed to do something, and that something was
to lead the team in acquiring new skills while at the same time supporting the
project. We did look at the use of external OCM resources, but the price tag was
astonishingly high and hadnt been budgeted for, and so this idea was rejected.
Instead, we embarked on researching good OCM material, inviting external experts
who were willing to speak to the team in return for a good meal and some expenses
and running workshops with the team to explore the OCM challenge and develop a
plan for change management.
The result, although perhaps not the perfect OCM engagement, was twofold: The
team learned a new skillor at least had their awareness raised over the need
to take OCM seriouslyand the business change impact was relatively smooth
(certainly better than had we done nothing). had we just managed the situation, Im
not sure what the outcome would have been. The fact that we led the situation was
a positive thing.
KEY LESSONS
1
BE A PROJECT LEADER, NOT A
PROJECT MANAGER.
Leadership is setting
a new direction or
vision for a group
to follow, while
management is
controlling resources
in a group according
to defned standards.
PETER TAYLOR
Peter Taylor is the author of two
best-selling books on productive
laziness: The Lazy Winner and
The Lazy Project Manager. In
the past four years, he has
focused on writing and lecturing,
chalking up more than 200
presentations around the world
in more than 20 countries, and
has been described as perhaps
the most entertaining and
inspiring speaker in the project
management world today. Peter
also acts as an independent
consultant, working with some
of the major organizations in
the world, coaching executive
sponsors, project management
ofce leaders, and project
managers.
PROJECT LEADERSHIP, NOT PROJECT MANAGEMENT
Owner / Director at The
Lazy Project Manager Ltd
Twitter I Website I Blog
b
14
A
current trend is to highlight increased engagement of project
managers (PMs) to help drive strategic initiatives. Organizations
need to be more agile, customer focused, and innovative to stay
competitive in the global marketplace. A few years ago, I had the
opportunity to work as a PM and systems engineer on one of the
largest Medicaid data warehouse projects in the United States. The project was
complex; highly visible; and had multiple stakeholders, virtual teams, and remote
data centers of excellence. The U.S. Department of health Care Services (DhCS)
had an urgent need to implement and deliver a 21st century business intelligence
(BI) system. Stakeholder engagement was the key to producing results and positive
outcomes for this project.
What key leadership tenet did I use? Swift trust. PMs and program managers live
this every day: Agility is important for developing swift trust with teams, sponsors,
C-level executives, and stakeholders. Swift trust occurs when a diverse group is
brought together in a temporary organization, such as a project ofce or virtual
team created for an urgent project.
As a leader, you must earn trust quickly to infuence key stakeholders. Everyone
will start with little or some knowledge to gauge trust among the team. You must
demonstrate that you can be trusted and trustworthy. Team members must also
demonstrate their integrity and ability to be accountable, thus earning trust within
the group and from the leader. Why is this skill set important? According to recent
Project Management Institute research, building trust is a key trait that successful
PMs and program managers share.
Results and Outcomes
The BI solution went live on March 29, 2008, and that solution for DhCS is still
in production today. The project was designed to help more efciently manage
Californias $38 billion Medicaid program (known as Medi-Cal), save money for
California taxpayers, and improve healthcare services for millions of California
residents. It is the largest Medicaid data warehouse in the nation.
KEY LESSONS
1
2
AGILITY IS IMPORTANT FOR
DEVELOPING SWIFT TRUST WITH
TEAMS, SPONSORS, C-LEVEL
EXECUTIVES, AND STAKEHOLDERS.
YOU MUST EARN TRUST
QUICKLY TO INFLUENCE KEY
STAKEHOLDERS.
Swift trust occurs
when a diverse group
is brought together in
a temporary organiza-
tion, such as a project
ofce or virtual team
created for an urgent
project.
NAOMI CAIETTI
Naomi Caietti is founder and
CEO of TheGlassBreakers
and has been a consultant,
a published author, and a
recognized expert on personal
growth and leadership
development for project
managers for more than
10 years. She is a global
speaker and a featured
subject matter expert for the
ProjectManagement.com
community and was recently
interviewed by Samad Aidance
of NeuroFrontier on Leadership
for Women PMs. Naomi blogs for
LiquidPlanner and is the author
of a chapter in Peter Taylors
book, The Project Manager Who
Smiled.
BUILDING TRUST ONE PROJECT AT A TIME
Project Manager /
Consultant at the State
of California
Twitter I Website I Blog
b
15
M
y story goes back 18 months, when my team and I kicked of
an implementation for a full-blown enterprise-level healthcare
system. The project involved multipoint integration and drastic
changes to current business practices. There were signifcant risks
and issues involving the design and build decisions. We also struggled to bring
more ownership to the project team to facilitate the focus required for the work.
We needed to tackle these challenges before they afected the critical path of the
project. Therefore, I divided my approach into leveraging three related concepts:
ownership, transparency, and accountability.
First, we focused on facilitating ownership. We made things easy and provided
incentives. We concentrated project data into our project management
information system, AtTask, for one-stop shopping. I authorized giving
stakeholders direct access to AtTask, which provides one-click automated hTML
email to communicate project information. It also serves as a forum for project
discussion, providing context, nurturing engagement, and driving ownership.
Second, we focused on transparency. We built late task reports, and AtTask
sent them out to the team via automated email on a weekly schedule. I included
stakeholders from all areas of the organization, not just IT and not just the team
members, which helped elevate stakeholder interest, bring transparency, and
break down silos, subsequently driving success.
KEY LESSONS
1
2
3
FACILITATE OWNERSHIP OF
PROJECT ELEMENTS.
BUILD TRANSPARENCY INTO
THE PROCESS.
ENSURE ACCOUNTABILITY.
I included stakeholders
from all areas of the
organization, not just
IT and not just the
team members, which
helped elevate
stakeholder interest,
bring transparency,
and break down silos,
subsequently driving
success.
TONY TOGLIA
Tony Toglia has been
involved in healthcare
technology, administration,
project management, and
leadership since 1987.
He currently manages a
project portfolio involving
computerized physician order
entry clinical, ancillary, and
business ofces at a growing
regional healthcare delivery
organization.
THE KEYS TO SUCCESS: OWNERSHIP, TRANSPARENCY, AND ACCOUNTABILITY
Director, Project
Management Ofce at
Rideout Health
Website
16
Finally, we focused on accountability. We used project scorecards
and dashboards to leverage the transparency into accountability. Our
biggest win was creating a custom issue category called decisions,
referring to decisions that were holding up design and build eforts.
The dashboard was grouped by senior leaders and displayed before all of them in
the boardroom. That transparency drove many executive decisions forward that
had been lagging to that point.
We saw a signifcant improvement in performance by leveraging a preexisting
tool in a way that facilitated stakeholder ownership, brought transparency to the
project, and displayed accountability. We brought focus and resolution to our
problem areas and got back on track.
KEY LESSONS
1
2
3
FACILITATE OWNERSHIP OF
PROJECT ELEMENTS.
BUILD TRANSPARENCY INTO
THE PROCESS.
ENSURE ACCOUNTABILITY.
I included stakeholders
from all areas of the
organization, not just
IT and not just the
team members, which
helped elevate
stakeholder interest,
bring transparency,
and break down silos,
subsequently driving
success.
TONY TOGLIA
Tony Toglia has been
involved in healthcare
technology, administration,
project management, and
leadership since 1987.
He currently manages a
project portfolio involving
computerized physician order
entry clinical, ancillary, and
business ofces at a growing
regional healthcare delivery
organization.
THE KEYS TO SUCCESS: OWNERSHIP, TRANSPARENCY, AND ACCOUNTABILITY
Director, Project
Management Ofce at
Rideout Health
Website
17
T
he clarifer often gets beat up at the beginning, but the sacrifce is
almost a necessity to bring project success in the end.
I dont begin a project until I fully understand it. This means that
I will sit with project sponsors and not proceed until I have nailed down their
vision. First, I must be able to describe the purpose of the project in two or
three sentences. Second, I should be able to describe the plan for the project to
anyone in a way that makes sense.
I often get beat up (fguratively speaking) on the way to getting my clarity. My
favorite story was when I worked for an Army contractor at the Pentagon. I came
into an enterprise application rewrite midway through and realized that the
project team was dancing around the need to get clarity for fear of the reaction
of a certain colonel. Unclear projects really cause stress, and on my frst day, a
few of my people burst into tears. Something had to be done, so over the course
of the next month, I gradually developed the toolsproject charter; updated,
accurate project plan; risk logand talked to the right people to get myself
in front of the colonel and his team. Ill never forget that experience: Even the
lieutenant colonels were nervous when the day of the meeting actually arrived.
Through the research we had done, the team realized that we needed to focus
on a concept that had been lost in translation while people communicated
around each other. That was the frst thing on our frst slide. Our colonel saw it
and started to turn red. Then, he banged his fst on the table so that the whole
room jumped. I must have been staring at him wide eyed when he bellowed,
Why didnt we fgure this out sooner? Then began a calm, efective conversation
during which we questioned him on scope, and we left the meeting knowing that
we had the clarity we needed to be successful.
KEY LESSONS
1
2
3
DONT BEGIN A PROJECT UNTIL
YOU FULLY UNDERSTAND IT.
BE ABLE TO DESCRIBE THE
PURPOSE OF THE PROJECT IN
TWO OR THREE SENTENCES.
BE ABLE TO DESCRIBE THE PLAN
FOR THE PROJECT TO ANYONE
IN A WAY THAT MAKES SENSE.
I dont begin a project
until I fully understand
it. This means that I
will sit with project
sponsors and not
proceed until I have
nailed down their
vision.
MICHIKO DIBY
Michiko Diby is probably the
most no-nonsense, get-it-
done project manager (PM)
clients will ever come across.
A process guru, Michiko
is a project management
professional and Design for Six
Sigma certifed. She can engage
at all levels but has a low
tolerance for obfuscation. She
has led projects and programs
for Fannie Mae, T. Rowe Price,
and the U.S. Army, and is the
author of a popular project
management blog, Kosmothink.
Michiko has been featured
in the Project Management
Institutes global magazine, PM
Today, and holds a masters
degree in Confict Analysis and
Resolution.
NAILING THE VISION: ENSURING PROJECT SUCCESS THROUGH CLARITY
CEO of The SeaLight
Company
Twitter I Website I Blog
b
18
T
he news was grim. The nine-month IT project, designed to deliver
a wealth of new cost data to a group of critical business users,
was six months into the scheduleand still gathering requirements.
Although some technical work was underway, the team was
foundering in how to settle the scope and proceed. Meantime, millions of
dollars in additional proft per week from better product pricing decisions the
new data would enable were being lost. And fnishing the technical work on time
was looking like an impossible dream.
But with less than three months to go, this project recovered. It was actually
recovered on one specifc day, when the sponsor, project manager (PM), and
team gathered with two key business users and laid out the state of the project.
The PM and sponsor called the meeting, because they had realized that the
team meant wellthey were trying to make sure they identifed all the customer
requirements so that they could deliver a full tool for the pricing analysts. But
therein lay the problem: They were gathering all the requirements as abstract,
equally weighted items to satisfy rather than focusing on the driving business
goals and what mattered most for achieving them.
That day, the group explored what mattered most to the analysts ability to make
better pricing decisions and reap the maximum amount of extra proft. By the
afternoon, the group had identifed the fve most important metrics the pricing
analysts needed from the sales and customer support data. The technical team
had started reworking the remaining schedule to deliver just those fve metrics.
In the end, the project was delivered within two weeks of its original deadline.
This project was not saved by heroics or more resources or tighter schedule
management. What turned the project around was business-focused leadership
by the sponsor and PM as well as business-focused collaboration by the team to
defne and pursue what mattered most.
KEY LESSONS
1
2
3
THE SPONSOR, PM, AND TEAM
SHOULD GATHER WITH TWO
KEY BUSINESS USERS TO LAY
OUT THE STATE OF THE PROJECT.
DETERMINE WHAT MATTERS
MOST TO THE PROJECT AND ITS
USERS.
BUSINESS-FOCUSED LEADERSHIP
BY THE SPONSOR AND PM CAN
SAVE A PROJECT.
What turned the
project around was
business-focused
leadership by the
sponsor and PM as
well as business-
focused collaboration
by the team to defne
and pursue what
mattered most.
CINDA VOEGTLI
Cinda voegtli is founder and
CEO of ProjectConnections.
com, an online resources and
support service for more than
350,000 managers and team
members worldwide. She
has more than 20 years of
development and management
experience and advises
companies of all sizes on
practical project processes. Her
passions are achieving just
enough project management
that makes sense and gets
used; building business-savvy
cross-functional teams; and
helping project managers bring
together the skills and attitudes
that make them truly great
project leaders.
BUSINESS-FOCUSED LEADERSHIP
CEO of
ProjectConnections.com
Twitter I Website I Blog
b
19
W
eve all heard phrases like common sense aint that
common, the sum of the parts, and its people that
deliver projects, and few would disagree with the sentiment
behind them. Yet, it never ceases to amaze me how few people
take these wise words to heart when managing projects, no matter how large
or small.
Ive been fortunate enough to be involved with some really successful
projects as well as some remarkable failures, and the common denominator
among those considered successful is typically the people involved. My not
so secret secret refects this.
The role of the project manager (PM) is frst and foremost to create an
environment in which the PMs team can be successfulnothing more,
nothing less. Take, for example, team building. Everyone recognizes the
importance of an efective team, yet how many of us make provision for this
in our plans and take the time to understand and play to the key strengths of
the team?
I was involved with a truly remarkable project in which the upfront investment
in team building paid dividends. The Wild Dogs (a name that the team
chose for themselves to refect their determination to work efectively as a
team) were able to deliver truly remarkable results in the most challenging
of circumstances. Although the teams success can be attributed to several
factors, including collocation, a willingness to invest in the teams development,
and a real sense of passion, it was without a doubt the unconditional support
for fellow team members that allowed magic to happena lesson we can all
learn from the teams namesakes in the wilds of Africa.
KEY LESSONS
1
2
THE TEAM IS THE KEY TO
PROJECT SUCCESS.
THE PMS PRINCIPLE ROLE IS TO
CREATE AN ENVIRONMENT IN
WHICH THE TEAM CAN SUCCEED.
The role of the
PM is frst and
foremost to create
an environment in
which the PMs team
can be successful
nothing more,
nothing less.
CHRIS FIELD
Chris Field joined Piksel Inc.
in March 2014 to establish its
Global Project Management
Ofce (PMO). he is passionate
about project management
and is an active member of
the UK Board of the Project
Management Institute,
having served as president
from 2009 to 2011. Chris
founded and is responsible for
organizing Synergy, one of the
largest project management
conferences in the United
Kingdom. He is also a Fellow of
the British Computer Society
and Member of the Association
for Project Management.
WILD DOGS AND PMS: TEAM BUILDING FOR SUCCESSFUL PROJECTS
Global PMO Manager at
Piksel Inc.
Twitter I Website
20
W
e were hosting more than 2,000 websites on an antiquated
platform when the decision was made to migrate them to a
new environment. The websites had been built over several years
using diferent standards. We did not have the staf for such a
challenging task, so we hired a new team, including an ofshore group. The leads
were skilled but did not have large-scale project experience. The traditional
approach to project management was not going to succeed. So, how did we
accomplish this in nine months? Preparation, visibility, empowerment.
What was the process? We wrote a program that created each new website
and entered it into our tracking software. A project coordinator was assigned to
evaluate the new website, and updates to copy and design were implemented
as needed. The quality assurance (QA) team then received the website for
testing. Any issues found were logged and assigned to a development team.
With the onsite and ofshore teams working together, most websites were
tested and fxed in a day. When teams came across situations they didnt know
how to handle, the issues were logged and assigned to management. We had
weekly training sessions with the teams, teaching them how to handle issues
on their own. After a few months, the teams were functioning without upper
management.
To accomplish this much work in such a short time takes preparation. We
had supporting software, workfows, reports, and queues in place before
we hired any staf. A large-scale initiative also requires visibility. Our reports
tracked progress in real time and sent us alerts if a project were stalled. Most
importantly, a busy team needs to be empowered. Instead of micromanaging
routine issues, we gave our people the skills to make decisions.
So, how do you migrate 2,000 websites in nine months? Preparation, visibility,
empowerment.
KEY LESSONS
1
2
3
PREPARE FOR YOUR PROJECT IN
ADVANCE AS MUCH AS POSSIBLE.
TRACK PROGRESS IN REAL TIME
TO ENSURE VISIBILITY.
GIVE PEOPLE THE SKILLS THEY
NEED TO MAKE DECISIONS.
A busy team needs
to be empowered.
Instead of
micromanaging
routine issues, we
gave our people the
skills to make
decisions.
FRANK GRIPPO
Frank Grippo graduated
from Purdue University
with a degree in Computer
Science. Starting his career
as a database and web
developer for Dialogic and
Healthstreet, he has since
been at LexisNexis for 13 years
and is currently the director
of Web Services. In LexisNexis
Web Visibility group, Frank is
creating websites to help law
frms market their businesses.
He is responsible for project
managers, developers, quality
assurance, and support stafs.
PREPARATION, VISIBILITY, EMPOWERMENT
Director of Web Services
at LexisNexis
21
L
et me start by admitting that I am not currently a project
manager; rather, Im writing from the perspective of an Agile
coach and trainer. This essay refects what I have seen while
working with clients over the past year.
The one remarkable leadership secret I have seen project managers
and Scrum Masters alike employ is the ability to communicate with senior
executives efectively. This sounds simple, but communicating with an
executive requires special skills that arent normally taught. It is not a type of
communication that happens naturally. It certainly requires impeccable logic,
confdence, and an ability to speak clearly, but it also requires more than the
obvious: It requires empathy and an understanding of the issues executives
face. This rarely considered idea is often the diference between the success
and failure of a conversation or idea.
The formula for communicating with empathy begins by framing the context
at the start of the conversation (In our organization . . . or On this project .
. .) and asking executives for their opinion (What do you see as our biggest
challenges? or What things do you see as risks?). having a conversation
about what worries the executive shows your empathy and respect for his or
her position. Trying to solve your problems without regard for the executives
problems will generally not produce positive results.
This leadership secret can move executives who were violently opposed to
an idea to support it after they understand how it would fx their problem,
too. If you have empathy for your executives and the things they are
concerned about, your ability to tie their problems to yours will allow you to
come up with solutions that solve both. Transform your conversations today
using this leadership technique.
KEY LESSONS
1
2
3
LEARN TO COMMUNICATE
EFFECTIVELY WITH EXECUTIVES.
FRAME THE CONTEXT AT THE
START OF THE CONVERSATION
AND ASK EXECUTIVES FOR THEIR
OPINION.
TIE YOUR PROBLEM TO THE
EXECUTIVES PROBLEM.
If you have empathy
for your executives
and the things they
are concerned about,
your ability to tie their
problems to yours will
allow you to come up
with solutions that
solve both.
BOB HARTMAN
Bob Hartman, known as
Agile Bob, has been involved
in the software industry
for more than 30 years.
He uses his experience to
help organizations, teams,
and individuals all around
the world. Bob is a popular
conference speaker, a certifed
scrum trainer and certifed
scrum coach, and is assistant
chairman of the Scrum Alliance
Board of Directors.
COMMUNICATING WITH EMPATHY
Certifed Scrum Trainer
and Coach at Agile For
All, LLC
Twitter I Website I Blog
b
22
I
once had to manage a team of electricians on a job site in the
Peruvian desert. I had never met those guys before, and they
only spoke Spanish (my Spanish is passable at best). In addition,
we had a tight deadline, leaving us only three days to complete
all the work. In those three days, I learned a lot about leadership, and the
secrets I uncovered stay with me to this day.
During our frst meeting, I had to explain what needed to be donethe
requirementsand why we only had three days to accomplish it all. At frst,
I started talking to them in English with the help of a translator. Because
I understand Spanish way better than I speak it, I quickly realized that my
translator was not conveying exactly what I needed to express. So, I decided
to switch to my frail Spanish.
As soon as I did, I noticed that the attitude of the team completely changed.
In their eyes, I went from being a Canadian who had arrived to tell them what
to do to a visitor who was speaking their language. Almost immediately, they
moved to a position of hosts and also realized that, though I was an engineer
project manager, there was something essential to this project (the Spanish
language) that they knew way better than I.
I went from boss, to someone who was in a position to learn from them.
Next, I explained how absolutely important their work was going to be to
make this project successful. We went over the requirements and started
working.
KEY LESSONS
1
2
3
TRY TO SPEAK YOUR TEAMS
LANGUAGE, EVEN IF YOU DONT
KNOW IT WELL.
DEMONSTRATE THAT YOU NEED
PEOPLE.
SHOW THAT YOURE READY TO
PITCH IN AND GET DIRTY.
Demonstrate that
you need people.
Doing so empowers
your team, humanizes
you as a manager, and
helps all stakeholders
own the project and
its success.
CESAR ABEID
Cesar Abeid is a certifed
project management
professional and has a B.E.Sc.
in Electrical Engineering from
the University of Western
Ontario. Cesar joined
Remontech in 2004, and
since then has successfully
implemented and managed
projects throughout Canada,
the United States, Brazil, and
Peru. He has a passion for
bringing project management
ideas to all. Cesar is also the
host of the weekly Project
Management for the Masses
podcast and the Construction
Industry podcast.
GOING FROM BOSS TO TEAMMATE
Project Manager at
Remontech, Inc.
Twitter I Website I Blog
b
23
Because our deadline was quickly approaching, I made another
decision that turned out to be important: I decided to join them
in their work. I suited up in personal protective equipment and
accompanied them into the feld, got dirty, and did some of the
work myself. The tasks were all completed within our timeframe, and I made
friends I am still in touch with to this day.
So, what were the leadership lessons here?
The answer is surprisingly simple. To lead, you need to try to speak your
teams language, even if you dont know it well enough. Demonstrate that you
need people. Doing so empowers your team, humanizes you as a manager,
and helps all stakeholders own the project and its success.
Finally, show that you are ready to do the work yourself, if needed. Show
that you are not afraid to roll up your sleeves and get dirty. This will earn
you respect and help you position yourself to compel all to do what needs
to be done.
KEY LESSONS
1
2
3
TRY TO SPEAK YOUR TEAMS
LANGUAGE, EVEN IF YOU DONT
KNOW IT WELL.
DEMONSTRATE THAT YOU NEED
PEOPLE.
SHOW THAT YOURE READY TO
PITCH IN AND GET DIRTY.
Demonstrate that
you need people.
Doing so empowers
your team, humanizes
you as a manager, and
helps all stakeholders
own the project and
its success.
CESAR ABEID
Cesar Abeid is a certifed
project management
professional and has a B.E.Sc.
in Electrical Engineering from
the University of Western
Ontario. Cesar joined
Remontech in 2004, and
since then has successfully
implemented and managed
projects throughout Canada,
the United States, Brazil, and
Peru. He has a passion for
bringing project management
ideas to all. Cesar is also the
host of the weekly Project
Management for the Masses
podcast and the Construction
Industry podcast.
GOING FROM BOSS TO TEAMMATE
Project Manager at
Remontech, Inc.
b
Twitter I Website I Blog
24
S
everal years ago, I moved into a senior program management role
at an Asian bank, managing a struggling steady-state enterprise
resource planning (ERP) installation. Luckily, I was friends with the
managing director of operations, who was able to give me the heads
up: Weve had other senior people in your position who focused on technical
competency and business acumen. The business tore them to shreds. Find
another approach.
Somewhat unnerved, I cautiously stepped into the role. There were all kinds of
functional problems on the ground. From my perspective, though, the single
biggest problem was a silo-based work culture. Everyone around me was smart
and talented, but those things clearly werent enough. To be able to make this
ERP system work, the organization as a whole needed to work as a single team.
Thats tough in a large, traditionally minded bank, and even tougher when
countless fngers are already pointing with hostile intent in every direction!
I started by cleaning up my own house. Using techniques Id learned from my
father (a schoolteacher), I set weekly customer-focused challenges for my people
that they had to solve in groups. For example, the risk management department
was regularly missing its morning risk reports. So: Find a solution that (1) lets us
notify them in person if the report will be late (before they go looking for it) and
(2) solve the late report problem. This had two efects: (1) We were fnally able
to get out in front of my customers issues across the enterprise and stop the
grumbling; and (2) my front-line customers went to their management (on their
own) to let them know they were seeing some interesting changes in my unit.
At this point, I had an opening to invite representatives from all of my customer
groups to the table to begin working on short-term capacity plans. The result?
high praise from my most demanding customer: Geof did in six months what
three vPs before him could not. he got those people to work together.
KEY LESSONS
1
2
3
AVOID A SILO-BASED WORK
CULTURE.
BEFORE IMPLEMENTING ANY
OTHER CHANGES, CLEAN UP
YOUR OWN HOUSE.
SET WEEKLY CUSTOMER-
FOCUSED CHALLENGES THAT
YOUR PEOPLE HAVE TO SOLVE
IN GROUPS.
Weve had other
senior people in your
position who focused
on technical competency
and business acumen.
The business tore
them to shreds. Find
another approach.
GEOFF CRANE
Geof Crane is a former senior
project portfolio manager
who has ties to some of the
worlds largest banks and
professional services frms. A
staunch believer in the value
of soft skills over hard skills, he
has returned to university to
pursue a doctorate in clinical
psychology. Unable to stay
away from the action, though,
Geof continues to help
aspiring executives organize
their project work and is an
adjunct professor of Project
Management at Durham
College in Ontario, Canada.
THE DEAL IS IN THE DETAILS
Doctoral Student,
Professor and Coach at
The Papercut Project
Manager
b
Twitter I Blog
25
T
he most successful project managers (PMs) possess leadership
abilities and employ them. As a military PM, it was a skill I learned
from watching the good leaders, and it was taught to us from the
beginning of our military journey. We were often required to brief
much higher-ranking ofcers about our projects.
Once, I managed the delivery, installation, data collection, and analysis of a
project to test solar photovoltaic panels as a back-up power source at remote
construction sites around the western Pacifc. This region included 14 sites,
stretching north and south from McMurdo Sound, Antarctica, to Adak, Alaska, as
well as east and west from California to japan and Subic Bay, Philippines. The U.S.
Department of Energy provided the solar systems, but the U.S. Navy SEABEES
installed, tested, and collected the data. Because this was a high-level government
project, it was high-visibility, watched by all levels of the chain of command.
The biggest challenge? Not only had no one on the project ever worked together
before, but we couldnt see each other. We conducted all communications over
ham radio gear. Today, we call this a virtual team, but in the early 1980s, that term
did not exist. So, how do you get a team of people who had never met face to face,
to get to know each other and work together? How do you conduct team-building
activities? Two words: virtual leadership.
I asked each team member to have a head-and-shoulders picture taken, then
send that picture to the 13 other sites. I implemented the policy that when they
were speaking to another member of the team, they bring their picture up so that
the speakers could see each others face. I also conducted sessions in which we
asked questions and discussed the issues and challenges we faced. Finally, I had
an open-door policy, where any person from the team could come to me with
any issue, and we would openly and freely discuss it. The outcome was that when
we all came together at a base near Los Angeles, California, the team met as if they
had been working side by side the entire time. They discussed family, hobbies, and
common interests, because they already knew so much about each other.
KEY LESSONS
1
2
WHEN TEAM MEMBERS WORK
VIRTUALLY, HAVING A PICTURE
OF EACH TEAM MEMBER FOSTERS
BETTER COMMUNICATION.
MAINTAIN AN OPEN-DOOR
POLICY TO ENCOURAGE
COMMUNICATION.
The most successful
project managers
possess leadership
abilities and employ
them.
GREGG D. RICHIE
Gregg D. Richie, PMP, CNP,
MCTS, is a full-time instructor
for Project Management
Academy. He also teaches for
the University of Washington
in the Project Management
Certifcate Program, has written
two books on Microsoft Project,
and is a 20 year veteran of
the U.S. Navy SEABEES. his
copyrighted signature saying
is, Goals are like underwear:
You have to change them once
in a while to feel better about
yourself.
VIRTUAL LEADERSHIP
Instructor at Project
Management Academy
Twitter I Website I Blog
b
26
F
or many years, I worked in a fast-paced brokerage frm in
Manhattan that had more than 1,000 developers working on
concurrent projects. Sometimes, they had to move in code changes
on the fy midday, while stocks were trading. And sometimes, these
changes had bugs that had to be eliminated immediately to prevent trading with
the wrong calculations. Sound chaotic?
To bring order to this cowboy environment, our chief information ofcer (CIO)
issued an edict that the developers must start using a new change management
system for all future software changes. This CIO was highly respected and
enjoyed all the forms of power one might fnd on the Project Management
Professional test: formal, punishment, referent, but the developers put up
strong resistance, and the cut-over failed for more than a year.
I was put in charge of converting the developers to the system, and I created
a hands-on class that I made all about the WIFM factor (Whats in It for Me?).
I showed the developers that they would beneft greatly from the system,
especially because of its autoback-out option. This feature meant that the
next time a developer would get a 3:00 a.m. call to back-out one of his or her
changes, that developer would no longer need to scramble around looking
for the old version of the code. If he or she had entered the change through
our system, it could be backed out automatically. All the person had to do was
have management key in B for back-out. The developers found this to be an
appealing argument, because it would save them hours of major stress on every
back-out.
The beneft?
The result was the IT department went from almost 0% to 100% compliance,
bringing a huge drop in the number of defects in our production-trading
environment.
KEY LESSONS
1
2
SHOW PEOPLE HOW THEY CAN
BENEFIT FROM YOUR PROJECT.
PEOPLE ARE MORE LIKELY TO
COMPLY WITH CHANGE WHEN
THEY UNDERSTAND THE
BENEFIT TO THEM PERSONALLY.
I was put in charge
of converting the
developers to the
system, and I created
a hands-on class that
I made all about the
WIFM factor (Whats
in It for Me?).
JEFF FURMAN
jef Furman, PMP, is a highly
experienced IT project
manager and project
management instructor. He
managed software projects
for Fortune 100 frms in the
New York City area for more
than 15 years and currently
teaches project management
for New York University and
for the U.S. Army at Fort Hood
and other bases around the
United States. The second
edition of his book, The Project
Management Answer Book
(Management Concepts Press),
will be out in August 2014.
HOW WIFM RESCUED A FAILING PROJECT
Project Management
Instructor / PM Book
Author at NYU
Twitter I Website I Blog
b
27
C
ommunicating projects is more than information fows among
team members: Its winning the trust and support of key
stakeholders outside the team.
For any project to succeed, we need to take our stakeholders on a journey. This
journey starts where those stakeholders are in terms of how much they know and
how they feel about our project. It ends when they are where we want them to be.
Before people act in the way we want, they have to feel positive about what we
are asking them to do. Before they feel positive, they need to know the essentials
that will change their attitudes from negative or neutral. Thus, communications
becomes an escalator that we take our stakeholders up. First, we make them
aware of our project; then, we build their understanding. Next, we win their
support, then involvement. Finally, we ask them to commit to our project.
just focusing on information fows gives people an intellectual concept of our
project. Theyre familiar but have no emotional investment to support us and
ensure that our project succeeds. Thats assuming they pay attention to the
information we circulate.
A few years ago, I supported four projects, together transforming a multitude
of in-country systems and processes to a single European-wide system. One
project manager (PM) got the concept of stakeholder journey, and together we
developed a simple communications plan with stakeholder route maps at its
heart. The others didnt. One said, No need for communications; well just tell
them and theyll do it. Another PM pulled out a door-stop document and said,
I already have a comms plan. It was just for show. The fourth project team had
great fun creating entertaining videos and posters but no plan.
Only the frst project won wide stakeholder support and delivered new systems
that people willingly used from day one.
KEY LESSONS
1
2
3
ENSURE THAT STAKEHOLDERS
BUY IN TO YOUR PROJECT.
WIN STAKEHOLDER SUPPORT,
THEN THEIR INVOLVEMENT.
ASK STAKEHOLDERS TO COMMIT
TO THE PROJECT.
Communicating
projects is more
than information
fows among team
members: Its winning
the trust and support
of key stakeholders
outside the team.
JO ANN SWEENEY
Jo Ann Sweeney is a
communications consultant
known for her results-
focused approach, rapport
and consensus building,
and clarifying complex
information. An FCIM and FIIC,
she specializes in working
with complex project teams
that have focused on the
technology solution rather
than its delivery. jo Ann
helps them get key people
committed so that the project
delivers the expected business
goals and wins recognition
for a great job. In addition,
she runs communications
training for project teams and
mentors leaders who have
communication responsibilities.
View more at: Communicating
Projects System
WINNING STAKEHOLDER SUPPORT
Founder of Sweeney
Communications Ltd
Twitter I Website I Blog
b
28