This document provides guidance on developing a concept paper for a technology-based instructional, training, or development evaluation project. It should address a real-world problem and propose an evaluation process to test a solution. The concept paper needs to include sections on the purpose and rationale, needs analysis, constraints, knowledge areas, and a detailed evaluation plan. It must consider stakeholders, deliverables, budget, schedule, staffing, risks, and how results will be disseminated. The concept paper development process involves brainstorming ideas, conducting research, and planning ahead to propose a solution that can be implemented and its impact measured.

1. CONCEPT PAPER INFO
PROFESSOR MARINO
TECH 4320

2. CONCEPT PAPER IDEAS
• Concept should be technology based geared towards instruction, training, or
development.
• A real-world problem – consider upgrading or changing technology as an
example or new uses for technology.
• Should be an evaluation process that can be completed and produce results
that can be implemented and reported.

3. CONCEPT PAPER 1ST STEPS
• Brainstorm for ideas – idea should be determined by Week 4
• Formally write out your Concept Paper’s Purpose
• What is the reason for your evaluation project?
• Formally write out your Concept Paper’s Rationale [this section should and
can include references to support it]
• Conduct a Needs Analysis too!

4. CONCEPT PAPER
CONSIDERATIONS
• Constraints – scope, time, and cost [budget]
• Life cycle – how long will the entire process take?
• Knowledge areas – integration, risk, communications, and resources

5. CONCEPT PAPER
EVALUATION SECTIONS
• Initiation – Who? What? Is involved in the project.
• Planning – What are the steps in the process? How do you secure resources? When
do you secure resources? Who needs to sign off? The more detailed your plan the
better.
• Execution – How will you implement your plan? What will you need? When will you
do it?
• Monitoring and Controlling – implement your plan to your specific requirements and
collect data.
• Closing – report your data

6. CONCEPT PAPER PLANNING
• Think ahead
• Reflect
• Organize
• Prepare

7. CONCEPT PAPER NEEDS
ANALYSIS
• Determine if this evaluation is needed and why
• Determine what evaluation method works best with your concept and
why
• Identify the people impacted by this evaluation
• Identify any barriers to implementation
• Make sure you’re able to collect data and where you’ll get it from

8. CONCEPT PAPER DATA
• How will you collect data? Observations, questionnaires, etc.
• Who has the info you need to collect? For example, the data might be
online or may need to be collected.
• Determine how and who will interpret/analyze data. Different people
may do this differently
• Who will produce results based on the data?

9. CONCEPT PAPER NEEDS
• Stakeholders – who’s involved
• Deliverables – what’s needed to be produced to show the evaluation has
been implemented
• Budget and schedule – how much will it cost? How long will it take? Who is
paying for it?
• Staffing – who is working on this?
• Risks
• Assumptions

10. CONCEPT PAPER COMMUNICATE
• How do you disseminate all information?
• Who receives the information and Why?
• When do they receive the information?

11. CONCEPT PAPER DECISIONS
TYPES OF DECISIONS
• Optional innovation decisions
• Decision made by individuals, independent
of the system
• Collective innovation decisions
• Decision made by consensus
• Authority innovation decisions
• Decision made by a few individuals who
possess power, status or technical expertise
• Mandates
DECISION MAKING PROCESS
•Knowledge - Awareness
•Persuasion - Sell the
idea
•Decision - Yea or nay
•Implementation -
Launch
•Confirmation - Confirm

12. CONCEPT PAPER ADOPTERS
Rogers, E. (2003). Diffusion of innovations. New York: Free Press
Innovators – create the
idea
Early Adopters – are
easily sold on the
innovators idea and
support it from the
beginning
Early Majority – join
shortly after the Early
Adopters
Late Majority – join
when the process
implementation
proves successful
Laggards – only get
behind the project
when it is clear it will