What a relata de experiência methodology actually is
It's a structured way of writing about something you did in a real setting, not a thought experiment or literature review. You document the context, the choices you made, what happened during implementation, and what you would adjust if you had to do it again. Most people in engineering education and curriculum design write these without realizing they're following a recognizable format. The format itself has been around for decades in Brazilian and Portuguese academic circles, and it shows up in journals like Cadernos de Pesquisa, Revistas de Ensino de Engenharia, and various educational research outlets.
The core structure of a relato de experiência metodologia
A well-written one typically has five sections, though the exact order varies by journal. The first section establishes context. This means naming the institution type, course level, student population size, institutional constraints, and any relevant curriculum requirements. It sounds basic, but most rejection reasons I've seen come from missing contextual information, not from flawed methodology. When a reviewer cannot place where the work happened, the entire report loses credibility regardless of how interesting the findings might be. The second section describes the methodology. This is where you name the theoretical framework, the design approach, and the specific techniques you adapted or created. The critical detail here is that you explain why you chose this framework for this context, not just what the framework is. Anyone can copy a constructivist label onto a lesson plan. The report becomes useful when you show what specific constraints forced you to modify the standard approach.
The third section covers implementation. This is the longest part in most cases. You describe the sequence of activities, the timeline, the materials used, and the adjustments made mid-process. I typically spend the most time here because the value of the report lives in the operational details. A reader should be able to understand not just what you intended but what actually happened when six students missed a session or when the lab equipment arrived broken. The fourth section presents results. In experience reports, results rarely look like statistical tables. They look like documented observations, student artifacts, collected feedback, and measurable indicators that your particular context allowed you to track. The key is to present what you observed without immediately interpreting it. Save the interpretation for the next section. I've seen good reports weakened because the author couldn't separate observation from opinion.
The fifth section is the discussion and reflection. This is where you connect your experience to existing literature, acknowledge where your results aligned or diverged from published work, and explicitly state what you would change. The reflection part is what separates a true experience report from a project description. If you finish without addressing limitations and adaptations, reviewers will notice.
A specific problem I ran into and how I handled it
About three years ago, I submitted a relato de experiência metodologia to a peer-reviewed journal focused on engineering education. The reviewers objected to the qualitative nature of the data. They wanted statistical validation, p-values, and a control group. The project was conducted in a private engineering college with forty-two second-year students across two concurrent sections. The methodology involved a modified problem-based learning cycle applied over eight weeks. There was no control group because the department required all sections to follow the same updated curriculum simultaneously. I spent two weeks wrestling with how to respond. The final version of the report included an explicit methodological justification section that cited established literature on qualitative educational research and the epistemological positioning of experience reports. I added a limitations subsection stating that the study was exploratory rather than confirmatory, and I reframed the results as descriptive findings with supporting student artifacts and instructor observations rather than attempting statistical inference. The journal accepted the revised version. The lesson was straightforward: when reviewers demand a different evidence standard, address it directly in the text rather than trying to retrofit your design to fit their expectations.
👉 Clique no botão abaixo para saber mais sobre o assunto!
Counter-intuitive details most guides skip
First, experience reports often get undervalued in academic evaluation systems because they lack quantitative rigor, yet they frequently capture implementation failures that randomized controlled trials systematically filter out. A randomized trial tells you what works under controlled conditions. An experience report tells you what breaks when thirty students show up exhausted before a lab session and the projector fails. Both matter. Neither replaces the other. Second, the distinction between a lab manual exercise and an actual experience report is thinner than most writers assume. A lab manual describes a procedure designed to produce a known outcome. A relato de experiência methodology documents a procedure where the outcome was uncertain and the methodology itself evolved during implementation. If your report reads like a recipe, you wrote a procedural description, not an experience report. The reader needs to see the moments where you deviated from the plan and why.
Common mistakes that weaken a report
Over-documentation is the most frequent issue. I see drafts that run forty pages because the author included every piece of background literature, every slide deck, and transcripts of student interviews. A focused fifteen-page report with clear arguments and specific examples consistently performs better than a sprawling one. Cut the literature review down to the sections directly relevant to your methodological choices. Remove anything that does not help the reader understand what happened and why it matters. Retrospective reconstruction is the second most damaging mistake. Writers often clean up the narrative after the fact, presenting a linear sequence of events that never actually occurred this way. The methodology section reads as if every decision was deliberate and planned. In reality, most implementations involve improvisation, mid-cycle adjustments, and moments where the instructor had to pivot because the class was lost. I keep dated field notes during the actual implementation and write the report from those notes rather than reconstructing events afterward. The resulting report feels less polished but carries significantly more credibility with experienced reviewers.
Practical limits of this methodology
Experience reports are inherently context-bound. An approach that functions at one institution with a specific student population and resource level rarely transfers directly to another context, even a similar one. The methodology section may look identical on paper, but the constraints are different. A public federal university in São Paulo operates under completely different administrative and pedagogical pressures than a private college in the Northeast. Readers need this information to evaluate whether the report applies to their situation. The genre also suffers from publication bias. Most experience reports document projects that reached a stable endpoint. Projects that failed completely, were abandoned mid-implementation, or produced inconclusive results rarely make it into print. This creates a distorted picture in the literature where every reported experience appears to have reached a resolution. It did not.
Word limits in many journals range between three thousand and four thousand words, which forces difficult trade-offs. You must compress context, reduce the implementation description, and still leave room for the reflection section. This compression often strips away the very details that make the report useful. I recommend checking the target journal's guidelines before you invest significant writing time, and planning your structure around their specific requirements rather than assuming a standard format will fit.
When a relato de experiência metodologia is the right choice
This format works well when your primary goal is documenting a practical intervention in an educational or professional setting, when the methodology required adaptation to local constraints, and when the value lies in what you learned about implementation rather than in proving a hypothesis. It is less suitable when you need generalizable causal claims, when your data consists primarily of large-scale survey results, or when the publication venue requires quantitative experimental evidence. In those cases, a different research design serves you better. For practical purposes, a typical well-prepared report takes roughly two to three weeks of focused writing after data collection is complete, assuming you maintained notes during implementation. Without those notes, the process doubles in time because you are reconstructing events that already passed. The method itself is straightforward, but the discipline required to be honest about what broke and what you changed is what separates useful reports from decorative ones.
