Society is becoming ever more reliant on digital solutions – even delivering anesthesia.  This is certainly evident in project management; although Microsoft Project leads the top 20, there are literally hundreds of others available.

PSI trainers often hear of enterprises looking for the “silver bullet” software solution, but our mantra is “Software doesn’t lead projects, people do.”  The human element is what drives project success; even the most powerful and sophisticated software will fail if:

• Project managers can’t strike the right balance of project oversight and either micromanage or under-manage.
• Project managers lack soft skills in people management, consensus building and communication.
• The people who will actually do the work have insufficient input into planning.
• The project charter and schedule are not updated, monitored or committed to by the teams and the project leader regularly (preferably every two weeks or less).

A company with the same problems no matter what software it uses may need a more comprehensive solution that goes beneath the surface.   But no matter what software option you choose, people will still be a decisive factor in the success of your project…at least until Skynet takes over.

Recently, several studies confirm what PSI trainers have long known. The dreaded “S” word – stress – can exhilarate –if handled correctly.

All too often, people procrastinate and downplay future challenges; as the deadline approaches, they panic. The results (and the teams!) suffer. However, introducing pressure sooner can actually decrease it in the long run, and yields better project results.

The key is shifting The Worry Curve early on, using PSI methodologies to empower team members to take control of their roles by:

•  Participating in planning and meeting the project’s requirements, challenges, deadlines and risks;
• Publicly committing to specific, well-defined project responsibilities;
• Meeting every two weeks to report on their progress, identify problems, update the plan to include any required changes, and again, commit to their role in the project’s success.

Problems are solved along the way (not at deadline), by teams invested in their roles, in the team as a whole, and in the project’s success. Eventually, the project ‘crosses the hump” and the worst is over, instead of just beginning.

At this point…believe it or not, many team members look at their roles in the project in terms of the “F” word: Fun.

Impossible? To learn more about the Worry Curve and how it works, contact us.

There’s no consensus on the economic cost of job burnout (sustained, chronic stress), but some estimates top $300 billion. Burnout’s toll on individual projects, or project portfolios, can be equally dire – missed deadlines, reduced project quality, budget overruns and diminished career prospects.

Every project manager probably knows some of the signs of burnout in themselves and their teams…but how many know some of the signs that burnout is about to happen?

• A deadline that get pushed ahead to make a sale, land a contract, beat a competitor, or launch at a trade show, without project team input.

• Pre-planning and charter development without the active input of all stakeholders and team members on risks, potential problems and timeframes.

• Inadequate consideration by managers and team members of the impact of their other professional and personal commitments to the project schedule.

Projects succeed when team members feel a real stake in the process, in the project, in their role and in the team itself. The Project Success Method energizes teams and keeps them energized from the beginning of the project to the end…ahead of time, and on budget.

Happy summer. Your project is about to get disrupted.

Summer brings vacations, kids free from school, office summer hours, and weddings.  It disrupts the flow of business (up to 20 percent decrease in productivity and a 13 percent increase in project turnaround times).  Global projects are particularly vulnerable to The Summer Syndrome, since many workers abroad often vacation at the same time, in August.

In the U.S. not everyone will vacation at the same time…but that’s a mixed blessing. A string of vacations taken throughout summertime creates a ripple effect as the project progresses. Decision makers, team members, vendors, consultants, shippers, payment processors – every function and business segment is affected.

That’s a compelling argument for the Project Success Method’s duration based project planning.  Our seven-step duration estimating process helps team members devise real-world timeframes (in which people go on vacations, for instance), while our add-in for Microsoft Project give managers more control of the schedule.

Of course project managers must still monitor for schedule slippage to prevent the Summer Syndrome.  However, the right tools and realistic scheduling can help make projects and teams have it “made in the shade” clear through to project completion.

One distinctive – but misunderstood – aspect of the Project Success Method is the importance of frequent, face to face meetings. Frequent meetings are too often considered productivity-killing time-wasters – there’s even an app for that.

Yet, time and again, we’ve found that face to face team meetings are the best way to get things done, especially if the ‘mechanics” of the meetings are right:

•  Schedule consistently, using the same dates/times. Apps can help; a comprehensive roundup is here.

• Be brief. After 45 minutes to an hour, focus plunges.

• Create an agenda, stick to it, lead it and end it on time.

• Stay on track. Note essential, but non-agenda concerns, and follow up after the meeting.

• Refreshments? Beverages yes; food no.  Dehydration hampers focus, but it plummets if attendees sit still for an hour in a crowded, windowless room while digesting lunch.

• No electronics or side discussions.

• Air concerns, questions, problems and solutions…but not complaints or whining.

These “mechanics” help create a successful meeting, but proper planning and people skills are key.  Together, these elements can make meetings less of a necessary evil and more of meeting of the minds.

There are two big creeps in project management that travel in pairs and always cause trouble: the expansion of the project called Scope Creep, and its traveling companion Schedule Creep, the extension of the project deadline.

Both creeps show up in projects with:

• Incomplete project scope development in the charter.
• Vague requirements from clients or management.
• Unauthorized scope and/or schedule changes and additions after the project’s start.
• Poor communication among the teams.
• Poor planning by team members.
• A lack of project control.

Handling both types of creeps calls for vigilance by the project manager. Diligent monitoring can nip some problems early, and requiring that approved scope changes are accompanied by revised estimates in time and budget can be helpful.

Entrenched issues – like an “impossible” new deadline or no budget for additional staff – need a comprehensive solution. PSI prevents both creeps from trashing projects with a ‘compression” technique; and ‘forward pass scheduling.”   As important, PSI helps maintain the team’s commitment to the project – even through additions or changes.

These techniques, taught in our two day training and described with case histories in The Project Success Method book, manages scope, scheduling and more, so you can enjoy the creeps where they belong – while watching a scary movie.

One expert says we’re in a Golden Age of Procrastination.  For project managers, this is hardly news.  However, if any particular project aspect or team is consistently late, it might be time to look under the hood. What is the procrastination telling you?

Some possible reasons:

• Teams or team members perceive a challenge to their ability
• Teams or team members see the tasks as unwelcome demand on their time
• Team members are pressured by their functional managers to work on other priorities
• Team members are not motivated
• A particular task has hit a bottleneck
• Team members have been drafted into a timetable they consider unrealistic

The Project Success Method offers three integrated management processes that prevent or address these issues with a clearly defined, thoroughly planned, and proactively controlled process during execution.  The linchpin, however, is our proven consensus building approach with the team members that builds real teamwork and –most important – encourages the team’s commitment to the schedule and the project.

Some scientists say we are hard wired for procrastination, but if you want better, faster project results…what are you waiting for?

There’s an interesting message hidden in the offerings at the upcoming Project Management Institute’s World Congress.  Classes in Technical Skills comprised only 18 of the 65 classes listed by “content aim;” the largest individual class category was not about Agile, or Change Management – it was “Leadership Skills for Project Managers, Program Managers and Portfolio Managers.”

It affirms our conviction, backed by a survey quoted by PMI, that people skills are a major factor in a project manager’ career.

Trends in leadership theories abound; Googling “Business Management Leadership Theories” yields nearly two million hits.  It’s easy to get tangled up in Theory Overload –

Management By Walking Around, Emotional Intelligence, and others flourish.  Whatever the theory, though, our years of experience confirm that the best project managers:

-Recognize that the most important element in a project is time

-Earn and maintain the trust of the project teams

-Inspire the team members commitment to the project with mutual support and individual accountability.

Those three points work together and will work with just about any theory, yielding successful projects and successful careers.

Although it’s Spring, the No Pants Festival has nothing to do with Spring Break and everything to do with an evolving management trend – the remote management of digital nomads. I call this type of workplace management “Radical Flexibility.”

The newest take on Radical Flexibility is ROWE (Results Only Work Environment).  The ideal ROWE workplace eliminates office norms: no set hours, no required meetings or office hours unless required to do your job.  The only measure of value is the results.

More accountability and less micromanaging are Project Success Method bywords, and some studies suggest positive impacts…but the underlying assumptions are less promising:

• you could get so much more work done if you didn’t have to bother with other people

• structure is a cage

A collaborative environment needs some structure – how can people work as a team without set hours? – and a meaningful team can’t be formed with people only known to each other as an email address.

The Project Success Method offers a better, hybrid alternative.  Our techniques encourage in-person meetings to strengthen mutual support, collaboration and commitment to projects – but individuals are free to decide whatever pace or solutions work best. The Method has worked for small new product launches and large-scale, mission critical, time-sensitive, cross functional projects across an entire enterprise – while combining accountability and freedom for individuals, teams and managers.

Now that’s what I call Radical.  But no, it’s not pants optional.

A survey of 32,000 employees revealed that people who met with their managers up to six hours a week were more inspired, engaged and innovative at work. That confirms PSI’s preference for in-person, biweekly team status meetings to shift the Worry Curve.

We know it’s difficult to make time, coordinate schedules, and reserve the room. However, consider the pitfalls of relying solely on electronic status reports – for project managers and teams:

• It encourages procrastination:  Emailed status reports and updates sit in an inbox with other email – easy to overlook or put off. It doesn’t command the attention a meeting would.

• It discourages group problem solving:  Electronic reporting deprives the project of the collective insight and support of the entire team when problems arise.

• It hinders accountability: The biggest problem electronic reporting creates is enabling team members to avoid public accountability for their tasks by hiding behind email.

In-person meetings create team commitment to the project, to each other and to their own roles in the project, while project managers find it easier to monitor progress, see deviations from the plan and tap the insights of the whole group to find solutions.  Being in a room together drives accountability, results, and a sense of community.

It’s a lot better than hiding behind an email.