Project team leadership is an even more important skill in today’s tight economic times making it even more of a shame when new, and even some experienced project leads fumble the ball in the name of their muddled agendas.
While doing more with less is quite a mantra these days, there are seven deadly sins of project leadership holding back once successful project teams from continuing to thrive.
It’s never fun watching a technical documentation, training development, or other writing projects get off to a false start or just downright fail. It can be a real morale blow and expose the writer(s) and their team to criticism from stakeholders. However, failures do happen, and it is best to do what you can to recover from quickly.
Writing projects can fail or stall for a myriad of reasons including poor planning, course changes in the project plan, and other risks that may or not be accounted for in the overall project plan.
Here are five ways to get past a failed or stalled writing project:
While covering project management and collaboration topics for CNET TechRepublic, I had the opportunity to write about Asana, a social task management platform. I liked it so much I started using to manage the editorial checklists I create for articles, blog posts, and corporate client projects.
When it comes to project teams, Asana is a viable substitute for email. I even recommend Asana to freelancers and independents who need to centralize their project task management.