Should my conference paper methodology read like a journal article?

You should aim for a methodology that captures the core logic of your work without the exhaustive, step-by-step procedural documentation typical of a full journal article. While a journal submission demands enough detail for a peer to replicate your experiment from scratch, a conference paper is primarily designed to spark discussion and demonstrate the feasibility of your approach. Because you have a strict 800-word limit, you need to prioritize the conceptual framework and the unique innovations of your design over the granular minutiae of every instrument setting or calibration step. Think of your methodology here as a high-level narrative that justifies your results rather than a technical manual for future researchers. If you try to cram the level of detail required for a journal into this space, you will likely end up rushing the analysis or discussion sections, which are often the most important parts for conference attendees who want to see the "so what" of your findings. The biggest misconception I see is that "standard format" implies a one-size-fits-all level of detail, but in reality, conference methodology sections are about strategic transparency. You should focus on the "why" behind your choices rather than just the "how." For instance, imagine you are testing a new composite material for aerospace components; in a journal, you would list every temperature ramp and chemical concentration in your curing process, but for a conference, you should focus on why you chose that specific curing cycle to optimize strength-to-weight ratios compared to existing industry standards. By focusing on the decision-making process, you provide enough context for the audience to understand your results while leaving room to discuss the implications of your work. If a reviewer or audience member needs to know the exact voltage of your sensor, they can always ask during the Q&A session or reach out to you afterward, which is actually a great way to build professional connections. There is a trade-off here between completeness and readability, and your priority should be the flow of your argument. If your methodology feels like a dry list of equipment, you are losing the chance to tell the story of your research. However, be careful not to be too vague; you still need to provide enough technical grounding so that your conclusions don't seem like they came out of thin air. If your specific field relies heavily on complex mathematical modeling, you might need to lean slightly more toward the journal style to prove your rigor, but even then, try to keep the focus on the novelty of your approach. Ultimately, your goal is to be clear, concise, and defensible so that your audience leaves the presentation understanding exactly how you arrived at your conclusions without getting bogged down in the weeds of your setup. Trust your instincts as an industry veteran to identify which parts of your process are truly critical to the validity of your results and focus your word count on those essential pillars.