A senior leader, Jim, emailed me to clarify how to track a project’s progress. He’s a sales guy by training and is now leading a technology-based company. He’s confused. When he asks about progress, he feels as if everyone takes one step forward and two steps back, just as in the Project Kisses of Death […]
When I sent my newsletter last month, Modern Management: Want Valuable Outcomes? Create Overarching Goals, several readers asked me questions. Why did I differentiate between outputs, outcomes, and benefits? I decided that was worth a blog post. Here’s how I define and use the terms. Outputs By themselves, a customer can’t use an output. We
Modern Management: Want Valuable Outcomes? Create Overarching Goals Organizations create all kinds of goals: for revenue, for the number of new and retained customers, and when they can release products. Then they cascade the goals “down” to individuals. When we create these individual “goals,” we create outputs. Even when we work with others, those outputs
I’ve seen several cases of process standardization recently. Those processes don’t translate to the current context. The processes don’t have sufficient agility to deliver the necessary results. Yet, people who want to use agile approaches don’t want to apply agile thinking to their processes. Some clients want to create their custom agile process— and then
You might wonder why I don’t start writing a proposal with a title. In my experience, a great title is something I need to ponder and experiment with. I do often start with a placeholder title. When I developed this multitasking talk, I used this title: Stop the madness. End the multitasking. That was a
Your bio establishes your expertise, authority, and credibility in your field. If your conference proposal has a speaking experience field, use that field to explain your expertise, authority, and credibility. I like to think of the bio and speaking experience fields as ways to connect with and invite the right people to your session: These
You know who your audience is because you framed the proposal. You started with outcomes, and you refined those outcomes when you wrote the abstract. Now it’s time to complete the rest of the proposal, excluding your bio and the title. Bios and titles are different from the rest of the proposal. (Those will be
You decided who your session is for: the people with the problems. You’ve got the outcomes. Now, it’s time to write the abstract. Conference proposals always have a short abstract. Some conferences, such as the Agile 20xx conferences, also have “Information for the Program Team.” You might think of that as the outline or more
Now that you’ve framed your proposal, start with what you want people to take away from the talk, the outcomes. Why? Because too many descriptions are a promise for an outcome or what people will learn. If you’re coy about the outcomes, people can’t select themselves in or out for your presentation. Speakers who say,
You want to present a talk, workshop, experience report at a conference. (Or, a lightning talk, Pecha Kucha, or more.) You have something important to share. How can you create a proposal that the program committee will accept? I’m writing this series to explain how to do just that. The series parts are: Understand who