Proposal Management Training Suite

Role

Lead Instructional Designer & Developer

Scope

• 7 elearning modules (~2 hours total)

Audience

• Newer proposal writers

Tools

• Articulate Storyline
• Vyond

The Challenge

The client was a large organization competing for business against smaller, more specialized firms. Proposal quality had become part of that competitive challenge, creating a need to strengthen proposal-managment skills among employees with relatively limited professional proposal-writing experience.

The project arrived with much of its scope already established: seven elearning modeuls covering key elements of the proposal lifecycle, approximately two hours of total seat time, and a requirement to combine interactive Storyline development with animated video. The curriculum would use Shipley methodology as its foundation while reflecting the client’s own processes and expectations.

The challenge was turning that broad mandate into a focused learning experience.

The source material was extensive: a comprehensive proposal methodology, existing proposal examples, client documentation, and input from multiple subject matter experts. The initial learning objectives provided direction but were too broad to drive individual learning experience. At the same time, seven modules had to fit within a limited total runtime and work both independently and as parts of a larger curriculum.

That created three immediate design pressures:

Build enough domain fluency to make informed design decisions. Proposal management was a new subject area for me. I needed to understand the methodology and the client’s application of it well enough to collaborate meaningfully with experienced proposal professionals—not just simploy transfer their source material into slides.

Prioritize the work over the methodology. The source material described a much larger discipline than two hours of training could, or should, cover. The curriculum needed to emphasize the practices learners would actually encounter in the client’s proposal process while giving less attention to methodologies and edge cases used only selectively.

Make limited practice time meaningful. Proposal writing depends on judgment, revision, and application. With a compressed runtime, interactions needed to do more than create activity on the screen; they needed to give learners opportunities to examine real examples, make decisions, practice improvements, and understand the reasoning benhind expert recommendations.

The goal was not to compress a proposal-writing manual into seven courses. It was to identify what newer proposal writers needed from that larger body of knowledge and turn it into learning they could actually use.

Discovery

The formal needs analysis had already been completed before I joined the project, so my discovery work focused on a different question: What did I need to understand about proposal management to design the learning effectively?

I began by reviewing the Shipley methodology, client examples, and existing source materials—not to master every detail, but to identify the concepts, terminology, and process relationshipst I needed to understand. I used those initial questions to guide a focused working session with an internal proposal-writing expert and establish a functional mental model of the proposal lifecycle.

That foundation changed how I could work with the remaining material. Instead of relying on subject matter experts to determine what belonged in each course, I could interpret the source content, propose an instructional approach, and bring targeted questions or recommendations back to the experts for validation.

From methodology to actual practice

One of the most important discoveries was that the source methodology and the client’s day-to-day process were not identical.

Shipley provided a comprehensive framework, but the client selectively applied parts of that framework depending on the proposal. For example, Pink, Red, Gold, and White color reviews were part of the client’s regular proposal process, while Blue, Green, and Black Hat reviews were used more selectively.

That distinction mattered. Treating every part of the methodology equally would have spent limited learning time teaching the framework rather than preparing learners for the work they were most likely to perform.

Making the objectives usable

The initial objectives also needed refinement before they could meaningfully guide the design.

For example, one objective for the Color Reviews module was:

Use Color Reviews effectively.

That described the desired outcome broadly, but it did not identify what learners actually needed ot understand or do. I decomposed it into more specific objectives addressing:

• When to use Pink, Red, and Gold reviews to improve and refine a proposal
• The purposes and goals of Pink, Red, Gold, and White reviews within the proposal process
• Where the client selectively used Blue, Green, and Black Hat reviews

• Original Objective

  Use Color Reviews effectively.

• Modified Objectives

  • Understand when to leverage Pink, Red, and Gold color reviews to improve and refine proposals

  • Explain the purpose of Pink, Red, Gold, and White color reviews and the goals that each has in the proposal process

  • Understand where [client] uses Blue, Green, and Black Hat reviews

The distinction between regular practice and selective practice then informed the course itself. The reviews learners would routinely encounter received most of the instructional attention; the others wewre introduced in proportion to their role in the client’s process.

Discovery was therefore not just about learning the subject matter. It established enough domain context to make deliverate decisions about what to teach, what to emphasize, and what to leave in the reference material.

Decision Framework

With seven modules sharing approximately two hours of total seat time, the curriculum could not treat every concept in the source material equally. I needed a consistent way to decide what deserved learner attention.

The primary question became: What does the learner need to understand or practice to participate effectively in the client’s actual proposal process?

I used that question to evaluate content across the curriculum.

Frequency over completeness

Concepts that appeared routinely in the client’s work received greater instructional emphasis that practices used only in specific circumstances. The goal was not comprehensive coverage of Shipley methodology; it was enough understanding to support performance in the client’s environment.

Application over exposure

When a concept required judgment, instructional time was reserved for examples, comparison, revision, and practice rather than additional explanation.

A learner did not need only a definition of a win theme, for example. They needed to recognize what made one effective, attempt to improve an example, consider an expert perspective, refine their work, and evaluate the result against the intended criteria.

Authentic examples over generic exercises

Wherever possible, activities were grounded in sanitized examples from the client’s own proposals. This allowed the learning to reflect the language, decisions, and challenges learners would encounter in their work rather than relying on generic examples created solely for the courses.

Independence without unnecessary duplication

Each module needed to work as a standalone learning experience while also fitting within a recommended seven-module curriculum. Foundational concepts therefore had a primary instructional home but could reappear elsewhere when learners needed them in context.

This allowed individual modules to remain usable on their own without turning ever course into a complete introduction to proposal management.

Together these decisions kept the curriculum focused on authentic work, meaningful practice, and the information learners were most likely to need.

Design Principles

Three principles guided the learning design across the curriculum.

Design for the work, not the source material

The source material established what could be taught; the client’s proposal process determined what deserved instructional attention.

Rather than treating the Shipley methodology as a course outline, I organized and weighted content around the decisions and activities learners would encounter in their work. Comprehensive methodology remained available as a reference, while limited course time focused on the concepts most relevant to performance.

Use interaction to create practice, not activity

Interaction was only valuable when it gave the learner something meaningful to do.

Activities were designed around the behaviors proposal writers needed to develop: identifying strengths and weaknesses, comparing alternatives, editing language, organizing process steps, and refining work against established criteria.

One activity, for example, asked learners to imrpove language by directly striking unnecessary or ineffective portions of a sentence. The interaction recreated the act of editing rather than converting it into a multiple-choice question.

A more extensive win-theme activity created a repeated cycle of practice and refinement. Learners created a win theme, reviewed expert recommendations, refined their response, and finally evaluated it against the goals of an effective win theme.

Making feedback part of the learning

Assessment questions didn’t stop at correct or incorrect. Feedback explained the reasoning behind the response so that every attempt could contribute to the learner’s understanding.

Depending on the activity, that reasoning appeared directly on screen or through an expert perspective embedded in the experience. Scored questions were distributed throughout each module at natural transition and reinforcement points rather than reserved for a traditional end-of-course quiz.

This allowed assessment to serve two purposes at once: provide evidence of learner understanding while continuing to build it.

Process

With seven modules to design and develop on a compressed schedule, a traditional linear development process would have added unnecessary handoffs between design, storyboarding, and production. Instead, I used a rapid iterative workflow, designing and storyboarding directly in Storyline and moving each module through the two-week development cycle.

Build the system before repeating the work

The first module established a reusable production foundation for the rest of the curriculum.

I created master slides and common layouts, standardized navigation and feedback screens, selecting recurring character treatments, and developed templates for introductory videos and other repeated elements. These patterns created visual and functional consistency while allowing later modules to focus on their unique content and interactions.

Reusable patterns provided the foundation, but individual learning activities were still designed around the instructional need. A custom editing exercise, for example, did not need to conform to a standard interaction simply because one already existed.

Design and develop together

Rather than creating detailed external storyboards and then rebuilding them in Storyline, I used the course itself as the working prototype.

This made it possible to evaluate content, pacing, interaction, and visual presentation together. It also reduced the distance between an instructional idea and a functional version that stakeholders could review.

Each module progressed through three client reviews:

• Review 1—Content and direction

  All instructional content was in place, most interactions were functional, and videos were represented by scripts and storyboarded supporting visuals. This gave stakeholders enough fidelity to validate the content, instructional approach, examples, and overall experience before final production.

• Review 2—Fully developed experience

  Interactions, visual treatments, audio, and videos were complete and fuctional. Review focused on the finished learner experience and any remaining refinements.

• Review 3—Final approval

  The completed module received final review and sign-off before delivery.

Use SMEs for validation, not first-draft development

As my understanding of proposal management developed, SME collaboration became increasingly targeted.

Instead of asking experts to supply finished instructional content, I brought them proposed explanations, examples, and activities with the reasoning behind my choices. A SME could then validate the interpretation, identify a gap, or refine the example based on deeper expertise.

This kept instructional ownership with the designer while using SMEs where their expertise provided the greatest value.

Validate before delivery

Every module moved through the rolling client-review cycle as well as internal quality assurance before delivery. Because stakeholders could review increasingly complete versions throughout development, final approval was the culmination of the process rather than the first time the client encountered the finished experience.

The result was a repeatable production workflow that supported rapid development without reducing every module to the same template.

The Solution

The finished solution was a two-hour proposal management curriculum organized into seven focused elearning modules. Together, the modules introduced newer proposal writers to the client’s proposal process and provided targetd practice with the decisions, reviews, writing techniques, and collaboration practices involved in developing a proposal.

Each module had a defined instructional purpose and could stand on its own, while a recommended sequence provided a broader learning path through the proposal lifecycle.

Seven focused areas of proposal management

The curriculum included:

Introduction to Proposal Management Training Established the foundation for the curriculum and introduced the proposal-management process.

Winning Business through Customer-Centric Win Themes Focused on identifying, evaluating, and strengthening win themes around customer needs.

Developing Customer-Focused Executive Summaries Explored how executive summaries connect customer priorities, proposed solutions, and persuasive messaging.

Conducting Proposal Operations Starting with Strong Kickoff Meetings Prepared learners to establish alignment, expectations, responsiblities, and direction at the beginning of the proposal process.

Persuading through Writing, Editing, and Graphics Applied principles for making proposal content clearer, more concise, persuasive, and visually effective.

Effectively Leveraging Color Reviews Connected the client’s review process to the purpose, timing, and expectations of individual color reviews.

Learning from Role Shadowing Supported continued development by connecting formal learning with observation and experience in the proposal environment.

Practice and assessment throughout the experience

Rather than separating instruction from assessment, each module distributed approximately five to ten scored questions throughout the learning experience.

Questions appeared at meaningful transition or reinforcement points and included explanatory feedback regardless of whether the learner responded correctly. Alongside scored questions, more open-ended interactions gave learners opportunities to analyze examples, edit content, compare alternatives, and refine their thinking against exper guidance.

This allowed the curriculum to move between instruction, application, feedback, and reinforcement rather than reserving practice for a final quiz.

A consistent experience without identical courses

A shared visual and interaction system connected the seven modules. Common layouts, navigation, feedback treatments, introductory patterns, and video conventions created consistency across the curriculum, while individual activities were designed around the needs of each topic.

Approximately 30 short animated videos supported the suite, ranging from brief explanations to longer instructional segments. Recurring learning-guide characters provided continuity, while animated representations of subject matter experts were used where an expert perspective supported the instruction.

The result was a curriculum that felt like a connected family of learning experiences wihtout requiring every module to follow the same instructional pattern.