| Course | MGMT 8920M Developing the Content Literature Review and Research Method and Design |
|---|---|
| Week | Week 10 |
| Paper type | Analysis plan |
| Length | About 590 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | PhD in Management |
| Updated | October 2026 |
Free sample paper for MGMT 8920M Week 10
Seven Steps From Transcript to Answer: An Analysis Plan Using Template Analysis to Study Why State Agency Technology Projects Accumulate Change Requests, Starting From Four a Priori Themes the Review Supplies, Checking the Template Against Change Logs and Naming the Trustworthiness Record
Student Name
Walden University
MGMT 8920M: Developing the Content Literature Review and Research Method and Design
Instructor Name
Month Day, Year
Seven Steps From Transcript to Answer: An Analysis Plan Using Template Analysis to Study Why State Agency Technology Projects Accumulate Change Requests, Starting From Four a Priori Themes the Review Supplies, Checking the Template Against Change Logs and Naming the Trustworthiness Record
Approach and Why It Fits
The study examines why technology projects at state agencies accumulate large numbers of change requests after contracts are signed, drawing on interviews with agency project managers and vendor staff and on the projects' change-request logs. The analysis uses template analysis. King (2012) describes it as a style of thematic analysis that allows the researcher to define some themes in advance, a priori, while revising them as the data are read, and that organizes themes hierarchically into a coding template. Brooks et al. (2015) note its flexibility in balancing structure with openness to new themes. That balance fits this study, because the literature review supplies four themes the analysis should test: unclear requirements, vendor contracts that price changes loosely, political pressure from agency leadership and weak change control.
The Seven Steps
Table 1
Analysis Steps, Outputs and Records
| Step | What it does to the data | What it produces | Record kept |
|---|---|---|---|
| 1. Familiarization | Read each transcript and the project's change-request log in full | Notes on first impressions per project | Familiarization memo per project |
| 2. Preliminary coding | Code transcripts against the four a priori themes, adding new codes where data do not fit | Coded transcripts | Code list with definitions, dated |
| 3. Clustering | Group codes into clusters within and beyond the a priori themes | Draft cluster map | Cluster map version 1 |
| 4. Initial template | Arrange clusters hierarchically into a template from a subset of four transcripts | Initial template | Template version 1, with rationale |
| 5. Template revision | Apply the template to remaining transcripts, revising where data do not fit | Revised templates | Log of every revision and its reason |
| 6. Document check | Compare template themes with the change-request logs for each project | Notes on agreement and divergence | Comparison table per project |
| 7. Mapping to research questions | Map final themes to each research question | Findings structure for chapter four | Mapping table |
Steps 3 to 5 repeat as needed; each repetition is recorded in the revision log.
What Each Step Adds
Step 2 is where the a priori themes are tested rather than assumed. A theme is retained only if the data support it, and any theme the data do not support is recorded as such rather than quietly removed. Step 5 is the heart of template analysis: each new transcript can expand, merge or split themes, and the revision log makes those changes visible. Step 6 uses the change-request logs as a check on interview accounts. If interviewees attribute most changes to unclear requirements but the logs show most requests arising after leadership changes, that divergence is itself a finding.
Trustworthiness
Lincoln and Guba (1985) offered four tests for naturalistic inquiry, which they named credibility, transferability, dependability and confirmability. The plan addresses each with a specific practice. Credibility is supported by comparing interview accounts with change-request logs in step 6 and by a second coder, a doctoral colleague, who will code three transcripts independently at step 2 and discuss differences with the author. Transferability is supported by describing each agency and project in enough detail for readers to decide whether their own agencies resemble those studied. Dependability and confirmability are supported by an audit trail: the dated code lists, template versions, revision log and comparison tables listed in the record column, kept together so that another researcher could follow how each theme developed.
References
Brooks, J., McCluskey, S., Turley, E., & King, N. (2015). The utility of template analysis in qualitative psychology research. Qualitative Research in Psychology, 12(2), 202-222. https://doi.org/10.1080/14780887.2014.955224
King, N. (2012). Doing template analysis. In G. Symon & C. Cassell (Eds.), Qualitative organizational research: Core methods and current challenges (pp. 426-450). SAGE. https://doi.org/10.4135/9781526435620.n24
Lincoln, Y. S., & Guba, E. G. (1985). Naturalistic inquiry. SAGE.
Reading the MGMT 8920M Week 10 instructions
For Week 10, write an analysis plan of about four pages. Name your analytic approach and explain why it fits, linking the choice to your literature review where possible. Present the analysis as numbered steps, and for each say what it does to the data, what it produces and what record you will keep. Explain what the most important steps add. Include a section on trustworthiness or validity, using an established set of criteria and naming the specific practices that meet each one. If you have documents as well as interviews, say how they will be compared. Write it so plainly that a second researcher could follow it and that your committee could audit it later.
Inside the MGMT 8920M Week 10 example
The change-request plan names template analysis and explains, citing King and Brooks and colleagues, that it allows a priori themes while staying open to new ones, which suits a review that supplies four. The steps table runs from familiarization through preliminary coding, clustering, an initial template and logged revisions to a document check and mapping themes to research questions, each with its record. A section explains that a priori themes are tested and kept only if supported, that revision is the heart of the method and that divergence between accounts and logs is a finding. The trustworthiness section matches Lincoln and Guba's criteria to the document check, a second coder, thick description and an audit trail.
Where the marks sit in the MGMT 8920M Week 10 rubric
Above all, the steps table is examined: each step's operation, output and record should be specific, in a sequence that fits the chosen approach. The choice of approach must be justified, ideally by the review; selecting template analysis without a priori themes, for example, would be inconsistent. The explanation of key steps earns credit when it shows how the analysis could surprise the researcher, such as themes not supported. The trustworthiness section is judged on whether each criterion is matched to a concrete practice. Plans that describe analysis in a single paragraph, name criteria without practices or omit how documents and interviews are compared fall into the middle band.
MGMT 8920M Week 10 help: mistakes that cost marks
Choose your analytic approach by asking whether your review gives you themes in advance; if it does, an approach that allows a priori themes fits. Write out each step as an action you will take with the data, and for each, decide what file or record will show you did it. Keep a revision log from the first day of coding. Plan how documents will check interview accounts. For trustworthiness, list the criteria and write one practice for each, such as a second coder or an audit trail. Be concrete; committees ask to see these records. A tutor can help you plan the steps, and the change-request analysis plan above shows the full table.
Get a MGMT 8920M Week 10 example written to your instructions
Pass along the Week 10 prompt and rubric, your research questions, the data sources planned and the themes your review established. An analysis plan written for another interview study, seven steps with a priori themes and trustworthiness tied to steps, is delivered in 24-48h; a first request is free. Its themes come from its own review, so the template yours starts from will differ.
More MGMT 8920M papers and PhD in Management samples
- MGMT 8920M Week 1: Discussion Post
- MGMT 8920M Week 2: Search Strategy
- MGMT 8920M Week 3: Literature Matrix
- MGMT 8920M Week 4: Theme Paragraph
- MGMT 8920M Week 5: Synthesis Draft
- MGMT 8920M Week 6: Gap Statement
- MGMT 8920M Week 7: Method Fit
- MGMT 8920M Week 8: Sampling Plan
- MGMT 8920M Week 9: Data Collection Plan
- MGMT 8920M Week 11: Chapter Assembly
- MGMT 8910M Week 10: Assembly Check
- MGMT 8003M Week 10: Peer Review Letter
- MGMT 8900M Week 10: Revision Memo
- MGMT 8009M Week 10: Debiasing Design
MGMT 8920M Week 10 questions, answered
Where can I find a free MGMT 8920M Week 10 sample paper?
The change-request analysis plan, seven-step table and trustworthiness section, is reproduced above.
Why template analysis in the MGMT 8920M Week 10 sample?
Because it allows a priori themes, and the review supplies four.
What are the four a priori themes?
Unclear requirements, loosely priced change clauses, political pressure and weak change control.
What does the document check add?
It compares interview themes with change-request logs, and any divergence becomes a finding.
How does the plan address trustworthiness?
With document comparison, a second coder, detailed description and an audit trail of dated records.