I had planned to call this article ‘The Nine-Step Strategy for Writing Summaries That Intrigue Readers’ but had a second look. It’s a bit long. And as this article is about writing headlines, summaries and abstracts, well… Let’s stick to the plan.
“An abstract highlights the key points you want your reader to remember after they’ve read your document.“
In Part 1 on Acquisition Planning, we provided an overview of the plan, identified who benefits, and some writing guidelines.
In Part 2, we’ll now go a little deeper and look at each part of the document.
If you’ve never written an Acquisition Strategy Plan before, this primer is for you. Acquisition Strategy Plans help guide organizations through the acquisition process, ensuring a well-defined approach that aligns with strategic goals.
In this four-part tutorial, I’ll show you how to setup cost calculation formulas in Excel to support your Cost Management Plan.
This week Laura and the team created a new Product Design Specification template. This is one of our series of templates related to product development, so if you’re interested in this area, please take a look at the product requirements specs and the user story template.
Last week I was talking to Laura, a supply chain expert working in Singapore, about an acquisition project she’s involved in. Essentially, she was tasked with helping it expand its operations. They need to quickly acquire new hardware and software for both the existing staff (about 60) and new employees soon to be onboarded (~25). […]
Today, we’re all working on projects. And most of those projects concern products. As consumers increasingly lean towards mobile devices and apps to use on-the-go, the demand to develop niche products to address this demand continues to rise.
This means that if you work in product development, or plan to move into this space, understanding how to spec out your product is essential. Our product-driven feature-rich culture requires tools like Product Requirements Documents to help teams align on product vision, features, and success criteria before and during development. So, where do you start?
Wouldn’t it be nice if your marketing plan aligned with other department’s activities?
One of the reasons it’s so hard to implement a marketing plan is that what you’re trying to do may clash with other dept activities, schedules, and deliverables. This often happens when there is a dependency on the software or product development team.
One way to resolve this is to map both plans, see where they align, and what gaps need to be filled. Here’s how to do it!
