DNP Project Methodology Help: Eight Decisions That Make Your Methods Repeatable

If your DNP methods section says "nurses will be educated and data will be analyzed", a committee cannot tell who does what. This guide is for doctoral students who have a problem and an evidence-supported intervention and now need a design, sample, protocol, measures and analysis plan. The eight decisions are design, setting, sample, intervention protocol, measures, data collection, analysis and fidelity.

MethodologyQI DesignEBP ImplementationMeasuresAnalysis PlanFidelity

Key Takeaways

Quick answer. Good project methods answer six questions: what design, where, with whom, doing exactly what, measured how, and analyzed how. If another clinician cannot repeat your project from the description, the section is not finished.

  • Choose the simplest design that can answer your aim, and name its limits.
  • Write the intervention as a protocol: who does what, how often, with which tools.
  • Give every measure an operational definition, a source, a frequency and an owner.
  • Decide the analysis before you collect data, and match it to the data type.
  • Plan to monitor fidelity, and log adaptations instead of hiding them.

Choosing a Design

Most DNP projects are quality improvement or evidence-based practice implementation projects, not experiments. Your design should be justified by your aim and by what the site can support. Ask your chair which designs your program accepts before you invest in a plan.

Common designs and when they fit

DesignFits whenStrengthLimitation to state
Pre and post (one group)You have a defined baseline and one siteSimple, feasibleCannot separate your change from other changes over time
Repeated measures over time (run chart style)Data can be collected weekly or monthlyShows trends and variationNeeds enough data points before and after
Comparison with a similar unitAnother unit will share dataAdds a reference for outside influencesUnits may differ in ways that matter
Pilot with feasibility outcomesYou are testing whether a change can be delivered at allLow risk, informs scale-upNot designed to prove effectiveness
Program evaluationA program already runs and needs assessmentFits real-world deliveryLess control over how the program was implemented

A quick decision rule

  1. If you want to know whether a process changed, use a design with a baseline and repeated measures.
  2. If you want to know whether a change is workable, add feasibility and acceptability outcomes.
  3. If you want to attribute an effect to your intervention, ask whether a comparison is realistic. If not, describe the design limits plainly.

Name the threats to your conclusions

Every design has weak points. Naming them in the methods section, and saying what you will do about them, is a sign of scholarly maturity. It also pre-empts the questions a reviewer would otherwise ask at your defense.

ThreatHow it shows up in a practice projectWhat you can do
Other changes over timeA new policy or seasonal patient mix changes the outcomeTrack known events on the run chart and discuss them
Staff turnoverPeople delivering the intervention differ from those trainedRefresher training and a quick guide for new staff
Measurement changeA record template or definition is updated mid-projectFreeze definitions or note the date of any change
Observation effectStaff behave differently because they know they are auditedUse routine data where possible and acknowledge the effect
Regression to the meanAn unusually bad baseline month naturally improvesUse a baseline long enough to show typical variation

Setting and Context

Describe the setting in enough detail that a reader can judge whether your results might apply elsewhere. Context is not decoration. It shapes what you can do and how well it will work.

What to describe

FeatureWhy it matters
Type and size of unit or clinicSets the scale of the change and the sample
Staffing model and shiftsAffects who can deliver the intervention and when
Patient population servedShapes inclusion, materials and outcomes
Existing electronic tools and templatesDetermines what can be built and what data exist
Competing initiativesRisks to uptake and to attribution

Keep facility details general enough to protect anonymity if your program requires it, for example "a mid-sized adult medical unit in an urban teaching hospital".

Sample and Criteria

State who is in the project and how they are chosen. In improvement work the "sample" may be patient records, patients, staff or all of these, so specify each.

Elements to include

A note on sample size

Formal power calculations are more common in research than in improvement projects. If your program asks for one, a statistician or your chair can help; our biostatistics guide explains the ideas. If it does not, justify the size by the volume available and the number of data points you need to see a pattern.

Recruiting and engaging staff participants

When staff are part of the project, describe how they are told about it and how they can decline. Voluntary participation is easier to protect when you do not supervise the people you invite. If you hold a management role, agree with your chair who will make the invitation.

  1. Present the project at a routine meeting, with a short handout.
  2. Explain what participation involves and what does not change if someone opts out.
  3. Give staff a way to ask questions or raise concerns without naming themselves.

The Intervention Protocol

Write the intervention so someone else could deliver it. Think of it as a recipe, not a description of an idea.

A protocol template

QuestionWhat to write
WhyThe evidence-based rationale, in one or two sentences with citations
WhatThe materials, tools and steps, in order
WhoThe role delivering each step and their training
HowThe mode, such as in person, by phone or in the electronic record
Where and whenThe location, timing, frequency and duration
TailoringWhat can be adapted, and what must stay the same

The TIDieR checklist, available through the EQUATOR Network, is a well-known model for describing interventions completely, and you can borrow its logic even if you are not required to use it.

Implementation supports

Need the methods section written to a reviewer standard?

Send your aims, setting and intervention outline with your brief, and we can draft or edit the methodology so each choice is justified. The price is shown before you pay, and every delivered paper includes 14 days of free revisions.

Get my instant quote →

Defining Measures

A measure is only useful if two people would count it the same way. Write an operational definition for each, including what counts and what does not.

Measure types

A measure specification table

MeasureTypeOperational definition (illustrative)SourceFrequencyOwner
Structured discharge teaching completedProcessProportion of eligible discharges with the teaching template fully documentedChart auditWeeklyStudent with unit analyst
Thirty-day return to hospitalOutcomeProportion of index discharges with an unplanned return within 30 days, per the organization's definitionQuality reportMonthlyQuality analyst
Time added to dischargeBalancingSelf-reported minutes added by the new stepShort staff formEvery two weeksStudent
Staff acceptabilityImplementationMean score on a brief acceptability toolAnonymous surveyEnd of projectStudent

Use validated tools where they exist. If you use a published instrument, cite its development and reliability evidence, and ask for permission when required. If you create a tool, say so, and describe how you checked that staff understood it.

How many measures are enough?

More measures do not make a stronger project. A small set that you can collect reliably is better than a long list you cannot sustain. As a general habit, choose one primary outcome or process measure, a small number of supporting measures, and one balancing measure. If your chair recommends a different mix, follow that advice.

Data Collection and Management

Explain who collects each item, when, and where it is stored. This is often the part committees find thin.

Plan for data quality

Privacy and storage

State whether data are de-identified, where files are kept, who can access them and when they will be destroyed. Follow your institution's rules and those of the site. The IRB and research ethics guide shows how to phrase this for an ethics application.

The Analysis Plan

Write the analysis plan before collecting data. It tells reviewers you will not go hunting for a result. Match each method to a measure and to a data type.

Matching analysis to data

Data type and questionTypical approachNotes
Repeated proportions over time (for example weekly completion rate)Run chart or control chart with median or meanNeeds several points before and after
Paired continuous scores, same people before and afterPaired t-test, or Wilcoxon signed-rank if not approximately normalCheck the assumptions
Two independent groups, continuousIndependent t-test, or Mann-Whitney UUse when pre and post samples are different patients
Two proportions, independent groupsChi-square, or Fisher exact for small countsReport counts as well as percentages
Paired binary outcomeMcNemar testSame people, yes or no at two times
Open-ended feedbackContent analysis with a simple coding frameShow how codes were developed

Statistical significance and practical meaning

Report effect size or the size of the change alongside any p-value, and remember that a small project may show a meaningful change that is not statistically significant. Say what change the site would consider worthwhile before you look at results. Your outcomes chapter, described in the outcomes evaluation guide, picks up from here.

Reading a run chart with simple rules

Run charts plot a measure over time with a median line. Improvement guidance from groups such as the Institute for Healthcare Improvement describes a few common rules for judging whether a pattern is more than chance. Confirm which rules your program follows, and apply them consistently.

SignalCommon rule of thumbWhat it suggests
ShiftSix or more consecutive points all above or all below the medianA sustained change in the process
TrendFive or more consecutive points all rising or all fallingA gradual change in one direction
Points on the medianDo not count them when checking a shiftAvoids over-reading the pattern
Unusual pointA single point far from the restCheck for a data error or a special cause

Fidelity and Adaptation

Fidelity is how closely the intervention was delivered as designed. Without it, you cannot tell whether a weak result means a weak intervention or a weak delivery.

Implementation outcomes to consider

Proctor and colleagues described a set of implementation outcomes that many projects borrow: acceptability, adoption, appropriateness, feasibility, fidelity, cost, penetration and sustainability. You do not need all of them. Pick two or three that fit your question.

Implementation outcomeSimple way to capture it
AcceptabilityShort staff survey or huddle feedback
AdoptionShare of eligible staff or visits using the tool
FidelityChecklist of protocol steps, completed during audits
FeasibilityTime per use, barriers logged
PenetrationProportion of eligible patients reached

Keep an adaptation log

Real projects change. Record each adaptation, the date, the reason and who approved it. That log turns a messy implementation into useful evidence.

Piloting Before Launch

A short pilot on a few patients or one shift finds problems cheaply. Test the training, the data form and the workflow, then adjust before the full start. Many students describe this as a small Plan-Do-Study-Act cycle.

  1. Plan: state what you expect to learn from the pilot.
  2. Do: run it briefly with a small group.
  3. Study: review data and staff comments.
  4. Act: fix the tools and confirm the launch date.

The Institute for Healthcare Improvement provides free guidance on this cycle and on the Model for Improvement.

Common feedback on methods and how to respond

FeedbackWhat it meansFix
"I could not repeat this."The protocol lacks detail on who, when and how.Add the protocol template and a one-page tool as an appendix
"Your measure is unclear."No operational definition.Add numerator, denominator, source and timing
"Why this test?"The statistic does not match the data type.Use the matching table and justify the choice in one sentence
"What about bias?"Threats to validity are not discussed.Add the threats table and your responses

A Worked Illustrative Example

The layout below is invented to show how the subsections fit together. It is not real data.

SubsectionIllustrative entry
DesignQuality improvement project with a pre-implementation baseline and weekly monitoring.
SettingOne adult cardiac step-down unit in a community hospital.
SampleAll adult patients discharged home during baseline and implementation; unit nurses as staff participants.
InterventionA teach-back discharge protocol delivered by the discharging nurse using a one-page tool.
MeasuresProcess: teaching documented. Outcome: return within 30 days. Balancing: minutes added.
AnalysisRun chart for the process measure, descriptive comparison for the outcome, thematic summary of staff comments.
FidelityWeekly audit of five records with a step checklist and an adaptation log.

Weak Versus Strong Wording

WeakStronger
Nurses will be educated about the tool.All unit nurses will complete a 20-minute session led by the project lead, with a one-page guide and a supervised first use.
Data will be collected and analyzed.The unit analyst will supply weekly de-identified counts; the student will plot them on a run chart and compare the baseline and implementation medians.
The project will improve outcomes.The primary outcome is the proportion of eligible discharges with complete teaching documentation.
Fidelity will be monitored.Five random records per week will be audited against a six-step checklist, and results will be shared at the weekly huddle.

An Illustrative Story

Illustrative example, not a real client. This short story is invented to show the pattern, and it contains no real people or numbers.

The problem. A student's methods section said, "Nurses will be educated and data will be analyzed."

The tension. The committee could not tell who would do what, and the site's quality analyst asked how each measure would be counted.

The turn. She wrote the intervention as a step-by-step protocol, built a measure specification table and tested her data form on a few records before launch.

The proof. The analyst confirmed she could supply the data in that format, and the committee approved the section without further changes.

The payoff. Implementation ran without a redesign, and a mid-project change was logged and explained instead of hidden.

Common Mistakes

Final Checklist

Frequently Asked Questions

Do I need a control group?

Not necessarily. Many practice projects rely on a baseline period. State what that design can and cannot show, and avoid causal language that it does not support.

Should I use qualitative methods?

They can add value, especially for barriers and staff experience. Keep them proportionate to the project and explain how you will analyze the responses.

What if my sample is small?

Say so and focus on descriptive results, run charts and practical significance. Avoid strong claims from tests with very few observations.

Do I need ethics approval for the methods I describe?

That depends on your institution and site. Ask early, and let the review body make the determination.

What reporting guideline should I follow?

SQUIRE 2.0 is widely used for improvement reports, and other guidelines exist for other designs. Ask your chair which one to use.

Methods a Reviewer Can Trust

Strong methodology is specific, consistent and honest about its limits. When each measure, step and analysis can be traced back to an aim, the committee can focus on your ideas rather than on gaps in your plan.

Want your methods section drafted or edited? Get my instant quote. The price is shown before you pay, every delivered paper includes 14 days of free revisions, and refund terms are on the money-back guarantee page. Please use any model paper in line with your institution's academic-integrity policy.