Welcome to the AtTask Blog for
work management technology

Browse our posts by category or by author. Subscribe to RSS feeds by author, category, or all posts. We love comments, so let us know what you think.

Three Keys to Help Manage the Queue

Any group that provides shared services within an organization must deal with project sponspors who think their project is the most important thing happening and deserve priority treatment—even if it isn’t or doesn’t. What’s worse, in many organizations, they often go directly to individual team members to get their work done first—chewing up time that should be spent on priority projects.

This distracts team members from their primary objectives, and they struggle to manage priorities. This is not only frustrating to project leaders, who soon realize that squeaky wheels in their organizations are really directing the team—the team is frustrated too.

Although there are organizations that have an active Project Management Office (PMO) and formalized processes for evaluating and prioritizing all inbound project requests—most don’t. Part of a successful project organization is effectively managing the queue of inbound projects.

Ironically, an approach that can help manage the queue can also provides project leaders with reliable information, engage the team, and create an environment where individuals can contribute at a higher level and take ownership of their work.

Regardless of how your particular organization tackles these challenges, an effective approach should include the following:

  1. It Works the Way People Naturally Work—enabling stakeholders to request work, suggest deadlines, collaborate and negotiate. Whether it happens formally or informally in your organization, these negotiations are going on right now anyway—you just might not be a part of the discussion. Creating a formalized queue for how requests are submitted and distributed to the team is critical. For some teams this might mean incorporating a more social feel to how work is requested or enabling dialog and negotiation (which usually transpires when work is assigned). Forcing people to work within a “process” that doesn’t feel natural will never be really effective.
  2. It’s Tailored to All Types of Workers—providing value to everyone on the team. For example, if the only value the team sees in a new solution is a better way for management to “watch what’s going on”, it won’t work. However, if everyone (including individual team members) can see some value, management will be able to seamlessly collect the project information they want—at the source. I’m convinced that providing a method or solution that provides value to the individual contributors on a project team is critical to fostering an environment with a free-flow of timely and accurate project information for informing decisions.
  3. It Portrays Work in Context—because projects aren’t the only work people deal with every day. If project leaders and their teams don’t have visibility into everything that’s going on and how it interrelates, it’s an incomplete picture. What’s more, information about tasks, projects and goals should be captured in a way that provides context. Although I don’t advocate implementing Twitter or Facebook into the process, a Twitter-like approach that attaches conversations to tasks and issues is incredibly valuable to leaders trying to make sense out of all the data collected within projects.

Over the years I’ve discovered that the solution to most issues I face in the workplace aren’t as complicated as I originally wanted to make them. I’m a big believer in executing the most simple solution that will get the job done. The same is true with today’s three keys.

If you already have a formalized process for evaluating potential projects (like Loyola’s process I mentioned a few days ago) consider yourself fortunate. If not, give these tips a try. Is there anything you can add to the list?

0 Comments »

Who Are You? Do You Really Know the Team?

I love puttering in my garage. No matter what else I’m doing on Saturday, I usually wind up puttering around on some project or another in the man cave. My wife would tell you that I am not the most “handy” guy she’s ever known (and she would be right), but I do like the notion of being “handy” and she patiently smiles and allows me my fantasies.

On the other hand, her father and older brother are two of the most “handy” guys I’ve ever known. They are highly-skilled carpenters and cabinet makers, but their skill with tools goes far beyond carpentry. In fact, I’m not too sure there’s anything that requires building or fixing skills they can’t do—they’re just wired that way. For years, I liked to blame my lack of  skills on the fact that I didn’t have the right tools for the job. Wandering through the hardware store I’m still influenced by that delusion and purchase the tools that I think will make me more “handy”—but it’s not the hammer, it’s the carpenter.

“All project management is people management,” said Tom Peters earlier this year at the Gartner PPM Summit in San Diego. I agree. My father-in-law wouldn’t lay the hammer or saw down on the bench and expect the tools to build the furniture—would you?

Over the years I’ve come to appreciate the value of the people on my team. As important as it is to create processes and practices, the linchpin to project success really isn’t the process, the project manager or the project management tools you use—it’s the individual contributor on the project team—it’s the people. As project leaders, our job is to make sure we are doing the best we can with the tools we have, or in other words, successfully lead the members of our project teams as we manage the process. Tom Peters also suggested that the culture we create on our project teams “isn’t just part of the game, it is the game.” And he argued, “If you don’t like it, you need to find something else to do.”

I couldn’t have said it better myself. When leading people, he suggested “…personal relationships are the fertile soil from which all success comes.”

Over the course of my career I’ve discovered that the key to success on any team (including a project team) depends on our ability to build and foster healthy and productive relationships with our colleagues. This is particularly true for organizations and project managers that rely on cross-functional teams where the project “leader” may have no direct-line authority over the team and must rely on his leadership skills or personal charisma to rally the team.

That’s not to say that only naturally charismatic people can experience this level of success. It all starts with learning who all the players are on the team, learning their strengths (and weaknesses) and leveraging their collective strengths to create the synergy needed to achieve success. Although this might sound over-simplistic, it starts with:

  1. Learning everyone’s name
  2. Understanding their backgrounds and skills
  3. Discovering what their career goals are and helping them achieve them
  4. Showing genuine interest in them as people (not simply as resources)

I once worked for someone who said that he worked very hard not to make a personal connection with his employees. He didn’t want the “baggage” associated with caring about the people who worked for him. Needless to say, he lived an empty and fairly shallow existence. My colleagues and I share the lion’s share of our time each day together and I’m convinced that it’s all about the people we work with, the people on our project teams and the challenges we share.

When project leaders really know the team, they can leverage their strengths and minimize their weaknesses, creating synergies that allow teams to be more productive, allow team members to maximize their contributions and organizations to ultimately be more profitable.

I’m sure there are those out there who don’t see the value of learning more about the members of the team, but as Tom Peters suggested, “All project management is people management,” and “If you don’t like it, you need to find something else to do.”

2 Comments »

10 Tips to Effectively Communicate With Stakeholders

Keeping an open and effective line of communication with stakeholders is important. A couple of years ago I stumbled on this list of tips for presenting to stakeholders, which is worth rehashing. Sometimes it seems like a thirty-minute meeting can be over in sixty seconds. Stakeholders sometimes have short attention spans, so if you don’t capture their attention in the first minute or two, they’ll start checking their email and watching the clock or worse—bail on your meeting.

Anyone involved in project-based work has to deal with sponsors and stakeholders. With that in mind, here are ten tips that might help your presentations:

  1. Pique their interest: An agenda is always a good idea, but a brief summary of what will be discussed is even better. Plus, it gives stakeholders a take-away and allows them to come prepared with questions.
  2. Don’t assume they know their job as stakeholder: They might understand the high-level view, but you will probably need to fill in the details.
  3. Keep it simple: Give them the situation in straightforward terms. Don’t overwhelm them with information. Cut to the chase. (However, be prepared for a deeper dive if they start asking questions.)
  4. Use numbers and pictures: PowerPoint is a great tool for presenting graphics and numbers to stakeholders. It’s how they present information to each other. You should too.
  5. Sometimes you have to use logic: Accept the fact that there might not always be data to support a particular situation. Not having numbers to back up your position could make a successful argument problematic, so you may have to turn to “if … then …” logic to shed light on a situation. However, don’t expect the same results or response from stakeholders—numbers rule with them.
  6. Waiting is never a good option: Don’t wait until a problem is obvious—it’s often more difficult to solve the issue at that point.
  7. Always offer a solution: If you are going to bring up a problem without offering a potential solution, you might as well tell the stakeholders, “Fire me now.” Finding solutions is part of your job as project manager.
  8. Specify the actions required of them: If stakeholders need to take action, don’t assume it will be obvious to them. Restate—in list form—what actions need to be taken and when.
  9. Always say “yes,” but make sure they understand how much “yes” costs: Sponsors and stakeholders don’t like to be told “no,” so don’t do it. Just make sure they understand the cost of their request, so they can judge for themselves whether or not “yes” is worth it.
  10. Don’t stop reporting status because stakeholders stop requiring it: Perception is reality. If stakeholders perceive that you aren’t doing anything—your not. Don’t let your head be the next one on the chopping block.

Regardless of your company’s work management methodology, there are a lot of project management tools available to help manage tasks and time-lines—some will help you more effectively communicate with the stakeholders in your organization. Whether or not your chosen project management tool facilitates that kind of communication, ignoring that important part of your role as project manager is dangerous. What do you do in your organization to encourage a positive relationship with stakeholders?

0 Comments »

“Tuning” Post Implementation

Having grown up in Colorado, skiing has always been a favorite past time in my family. While skis can be costly, my father taught me how to properly take care of them. It is just as important to tune and wax your skis periodically every year, as it is to buy the right equipment. Keeping up on the maintenance of a pair of skis is not only necessary for them to last longer, but also to help skiing performance.

Just as tuning and waxing a pair of skis is essential to have high performance while skiing, it is necessary to continually “tune” the way you work.

Post Implementation Consulting Team Lead, Dave Johnston, talks about the benefits, options and processes of consulting services after AtTask implementation to help stay waxed and tuned to achieve high performance.

Kristyn: Looking at the implementation, where does your role fit in the process?

Dave: The purpose of our team is to help customers once they’ve already gone through implementation. So after implementation, they may have taken a couple education courses, finished working with the consultant, and that’s where we come in. Often times, once people have been working in the tool questions will still come up but it may be more complicated than just needing basic support. Our team is able to help customize the support and walk clients through different obstacles if they arise.

Kristyn: How does the post implementation consulting work? Are there different packages?

Dave: After the consultant works with the client and time runs out we noticed sometimes there is still a need. So when you can’t use your consulting time anymore, you can still have the customer support that is personalized to your needs.

Secondly, there are three different packages: silver-25 hours, gold-50 hours and platinum-100 hours.  The time can be used on essentially anything the customer needs. We’ll do training, reporting building or sometimes a combination of the two. Having that extra time helps to walk people through it, explaining features along the way so they fully understand how it functions and how it works specifically for their needs.

Kristyn: How do you not only get in touch with a post implementation consultant, but also find out more about the packages?

Dave: Getting in touch with a post implementation consultant is easy. In the help desk there is post implementation queue where you can fill out the specific needs or complications, hit submit and AtTask contacts you. Also, to find more information on any consulting services, or the post implementation packages specifically, everything is at Community.attask.com.

1 Comment »

A Personal Stake in the Outcome

I recently finished reading Eric Ries’ The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. I included the subtitle because, Ries suggests, business leaders and project teams should consider themselves “entrepreneurs” and should be working to create the innovation that will make our organizations successful.

Not too long ago, I asked if it made sense for project team members to feel a sense of skin in the game, I believe it does. Ries suggests, that people “…need a personal stake in the outcome of their creations.”

Neither he nor I believe this always needs to be some kind of financial stake (although that sometimes makes a lot of sense), however even in organizations where a financial stake is unacceptable or impossible because the organization is a non-profit or government, “…it is still possible for teams to have a personal stake,” says Ries.

Ries describes how Toyota creates this sense of personal ownership and stake in the outcome with the role of shusa, or chief engineer:

Shusa are often called heavy-weight project managers in the U.S. literature, but this name understates their real roles as design leaders. Toyota employees translate the term as chief engineer, and they refer to the vehicle under development as the shusha’s car. They assured us that the shusa has final, absolute authority over every aspect of vehicle development.”

The shusa is responsible for the development of every new car from start to finish. In the late 70s I met an engineer at Toyota who was really excited to pull out the schematics of the quarter-panel he designed. My first thought as he describe how this was “his” quarter-panel was, “It’s a fender.” That “fender” happened to be recognized as part of the best engineered car in the world that year. All these years later, I admire his passion and sense of ownership. I don’t know if he had a financial stake, but his name was attached to the car and he definitely felt a personal stake in the outcome of that project.

When teams have a personal stake in the outcome of a project (whether financial or otherwise) they feel a greater sense of ownership, perform at a higher level and ultimately contribute to the success of their organizations. What are you doing to give your team a personal stake in project outcomes?

0 Comments »

The Value of a Social Network

Last night I made a presentation at an event sponsored by the Social Commerce Exchange. It’s not a project management group, but it is a network of people who share ideas, network and try to learn how to better leverage social media to accomplish the goals of their very diverse organizations. Not unlike the #pmot or #pmchat communities I enjoy interacting with about project management topics, I think there’s value looking outside of the PM community to get fresh ideas and learn new techniques. Because I’m an advocate of leveraging social media best practice within the project management process generally, learning what others are doing to communicate with their audiences is very informative.

Outside of project management, are there other communities you visit or forums you frequent? I’m a big believer of utilizing techniques and approaches from other industries that are successful (but possibly untried in ours), to increase productivity, improve collaboration and help individual team members maximize their contributions.

Attending events like the Social Commerce Exchange is part of what I do to improve my EVE ratio. Events like this often happen after work, I don’t get paid to be there, but I think it’s an important investment in my career. What are you doing to improve you skills and move the needle on your EVE ratio?

0 Comments »

Crude Confrontation Curtails Collaboration

There was a boy in elementary school who had a reputation for being tough and liked to bully the kids that were smaller or appeared weaker than him. He was the best athlete in our class, he could run faster, hit the softball farther and was definitely the strongest. Everyone was afraid of him. I was afraid of him.

As we got older and left elementary school he kind of slipped into anonymity. He wasn’t so tough anymore nor could he bully us anymore. In fact, I completely lost track of him and never really noticed him in high school.

Although grown-up bullies still exist, they aren’t quite as frightening as they were when I was in elementary school. Nevertheless, that type of brutish atmosphere isn’t very conducive to creativity and collaboration. However, even more than a bully, I think there is something else that makes it difficult for teams to effectively collaborate.

We work in an age of instant messaging, email and other almost instantaneous communication. We can’t let the immediacy of the medium allow us to become callous and casual in how we approach our co-workers, even when problems arise and mistakes are made. I believe that even in today’s workplace, there is a place for common (maybe not so common now) courtesy.

  1. Take time to make communication thoughtful and cordial: When timelines are truncated and project teams are asked to do more and more, take an extra few seconds when writing an email or other communique to consider that your communication is going to a person. I like to begin every email with a salutation, which reminds me that I am writing to someone. The extra two or three seconds it takes me to address the person I’m writing to doesn’t negatively impact my productivity, but it does help me foster a productive and cordial working relationship.
  2. Take time to be polite: Within the imperfect world of project-based work, sometimes difficult decisions take place. That doesn’t mean we can throw civility out the window. Over the thirty-plus years of my career I’ve watched what used to be considered common courtesy among superiors, subordinates and co-workers become “quaint” and considered “unnecessary.” There is nothing wrong with considering the feelings of someone needing correcting, regardless of how stupid you think they are or how big a mistake you think they’ve made. Being polite and considerate of each other is the very least we should be able to expect from our “professional” colleagues. Anything less is unproductive and immature.
  3. Remove the criticism from “constructive” criticism: I was taught early in my career, by friends and colleagues much wiser than myself, that “criticism” is never “constructive.” I don’t think I have ever worked with a project team that agreed all the time. Project management involves a lot of problem solving, which means that it’s seldom done right the first time. Fostering a creative environment where team members are creatively solving problems and pushing for excellence requires collaboration, not criticism. Where disagreements arise or a course correction is required, “I don’t like this,” should be followed by, “Here’s why, and here’s a suggestion as to how you might proceed.”
  4. Remember that critique is always easier than execution: It’s always easier to see the flaws from the outside looking in. Theodore Roosevelt said, “It is not the critic who counts: not the man who points out how the strong man stumbles or where the doer of deeds could have done better. The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood, who strives valiantly, who errs and comes up short again and again, because there is no effort without error or shortcoming, but who knows the great enthusiasms, the great devotions, who spends himself for a worthy cause who, at the best knows, in the end, the triumph of high achievement, and who, at worst, if he fails, at least he fails while daring greatly, so that his place shall never be with those cold and timid souls who knew neither victory nor defeat.”

Effective communication and collaboration doesn’t rely on tricks or gimmicks. In my opinion, it’s important to remember that effective communication is personal. It doesn’t matter if it’s face to face, via email, or even in a blog—its one person interacting with another. Project management tools can help facilitate this, but it’s really up to you.

American author and playwright Jean Kerr said, “Man is the only animal that learns by being hypocritical. He pretends to be polite and then, eventually, he becomes polite.”

What are you doing in your organization to encourage considerate and courteous interaction among your colleagues?

2 Comments »

What’s Your EVE Ratio?

I recently spoke to Tom Cooper of the Brighthill Group on the TalkingWork podcast. He’s a PMP who is now a speaker, trainer and coach who focuses on personal and professional leadership. Tom asks, “What’s your EVE Ratio?”

If you’re not sure what an EVE ratio is, you’re not alone. I didn’t know either. It’s the ratio of investment you make in education vs. entertainment. Tom suggests (and I wholeheartedly agree) that project leaders need to be investing regularly in their careers and leadership skills. If we content ourselves with the investment our companies are willing to make in us, we are being shortsighted.

I try to spend time every month either reading books, attending webinars or other events to help me become better at my job—and I’m willing to pay for it myself. Particularly with tight budgets and organizations less willing to pay employees for personal development, it’s important to continually make that investment in yourself. For example, over the last couple of years I’ve become a huge fan of Audible and take advantage of my commute each day to keep up to date on thoughts and ideas that will make me better at what I do. That being said, my EVE ratio is probably still weighted on the entertainment side.

Tom kindly shared his list of books, webinars, seminars and podcasts with the TalkingWork audience. We also want to make his Leadership Reading List available here.

Have you ever considered how much time and money you invest in entertainment vs. education? I’m pretty convinced that if you’re not willing to invest in your education and career, nobody else will either.

2 Comments »

The Social Project Manager

I’m a big believer is applying social media techniques within the project management process.

A little over a year ago I spoke with Elizabeth Harrin (@pm4girls) about her new book, Social Media for Project Managers. I understand it recently became available via Kindle, so I thought I would bring it up again. Whether you prefer the hard-copy or the electronic version of books, if you’re a project manager and want to wrap your head around what social media methods can do for you, I’d read this book.

Elizabeth takes the time to go through the different types of media, the pros and cons, along with discussing why you may or may not want to apply any particular media to your project management process. This applies to everything from podcasts, blogs, forums and webinars (but isn’t limited to those mentioned above).

I’m a pretty regular reader, and many project management books require a pretty dedicated desire to learn to get through—this one is decidedly different. Harrin’s writing is engaging and accessible. She’s a pro at making her ideas consumable to a pretty varied audience. This book should be on your bookshelf or in in Kindle library.

As you may already know, I’m a huge fan of implementing social media best practice into the project management process. I think taking those practices that have made Twitter, Facebook and other social media popular just make sense (particularly with so many Millennials in the the workforce today). I think the collaborative advantages of social media are pretty apparent.

If you want to create a more collaborative environment and you’re not considering a social media-like approach, I think you’re missing an opportunity to ramp up the collaborative ability of your project teams. I know of an engineering firm in Japan that is finding a lot of success in their efforts to eliminate email for project related communication and replacing it with the social component of their project management tool. I’m excited to follow how their efforts pan out over time.

Elizabeth suggests a great starting point for project managers who may be considering something like this. “Let’s start with establishing whether the project organization is … culturally prepared to take a dip in the social media waters.” She adds, “The first dependency to consider for your project-based social media activity is how much your team will want to participate in this. Web-based collaborative tools rely on people working online and being prepared to share knowledge. Ask yourself the following questions:

  1. How technically literate are your team members?
  2. Where are they based?
  3. How keen are they to try something new?

“A team already confident in using social media and online tools (in or outside the office) will make for an easier adoption of any such technology in the workplace. If you are working with a group of people who struggle to send emails, don’t text, and can’t use the calendar feature on their mobile device, you could find yourself meeting a technical challenge.”

This is great advice. The type of media you apply really does depend upon where your team is and whether or not it will actually provide value and help your team. What’s more, I don’t think age is the issue either. I’m a 50+ guy who is totally into the value of social media, while my wife doesn’t get it and doesn’t want to get it.

Is it right for your team? I can’t answer that one, but starting with Elizabeth’s book will help you make that determination for yourself.

0 Comments »

The Value of a Business Case

I just returned from Baltimore where I attended the  Mid-Atlantic Regional Conference 2012 of Educause. I was invited to co-present with Scott Sax of Loyola University regarding how they approach projects, operational initiatives and other work done within their IT organization. The presentation was well-received and it was certainly a pleasure to be associated with such an exemplary organization as the crew from Loyola.

Aside from our presentation yesterday, Rich Sigler, the director of the PMO at Loyola gave an excellent presentation about how he perceives the responsibilities of his PMO. the title of his presentation was: Technology Project Selection and Governance at Loyola University Maryland. It was outstanding, one of the best presentations I’ve seen on this topic.

He compared establishing a PMO to building a playhouse for his daughters. He suggested that the PMO needs the following four walls and roof:

  1. A portfolio of projects
  2. A project management process
  3. An information system
  4. A support strategy

He described how (in his opinion) the PMO’s responsibility was to promote a best practice approach to managing projects. I agree. Part of those best practices include how projects are selected for inclusion in the portfolio. It was a real commonsense approach to submission and prioritization I think is worth discussing here.

“Any member of the Loyola community can instigate a project request,” says Sigler. “The request is really a pitch that sells the idea of the project to the committee that makes decisions about whether or not any individual project will be pursued.”

Their governance committee evaluates any potential project based on some very simple criteria that includes “impact” and “effort”. They describe how projects are scored like this:

  1. Quick Win: High Impact/Low Effort
  2. Strategic: High Impact/High Effort
  3. Nice to Have: Low Impact/Low Effort
  4. Declined: Low Impact/High Effort

They also include in the evaluation whether or not there is a regulatory component or if the project is underway (those projects automatically take priority). The idea is to ensure that the project teams aren’t expected to do more than what they can realistically accomplish during the course of the average semester (which is their normal project timeline).

I like the nature of this simple approach. It gives them the opportunity to evaluate potential projects in a manner that everyone in the community can understand and gives potential project sponsors a baseline for making their project request.

Einstein once said something like, “Any idiot can make things more complicated, it takes real genius to make something simple.”

I think Rich and his team at Loyola have done that with this process. Of course, I’ve left out a lot of the details, but I’m convinced that the four walls and the roof they’ve build for their PMO “playhouse” puts them in a great position to prioritize and focus the project teams at Loyola on the work that will provide the most value to their organization.

What are you doing to prioritize projects and keep people focused on the things that are most important?

0 Comments »

© 2011 AtTask, Inc. All rights reserved.