Fusion Analyst

0430: AOR review, overnight message traffic. Flag anything that requires immediate update to standing products or notification to operations. 0600: wing standup support, brief if tasked. Deconflict the day's production priorities with the NCOIC. 0730-1100: direct production and supervising junior analysts' production. Review at least two junior-produced products and provide written or verbal feedback. 1100: pre-mission brief for afternoon launches — you are likely the primary briefer or the backup briefer. 1300: production continuation, coordination with theater-level intelligence organizations. 1500: mission planning support for next-day operations. 1700: debrief. 1800: admin and supervision tasks — EPR inputs, training records, CDC mentorship.

Monday: shop-level production review, identify gaps in coverage, assign production tasks for the week. Tuesday: focus on your specific AOR deep-dive work. Wednesday: mid-week check on junior analysts' production quality, course-correct as needed. Thursday: senior analyst or OIC meeting, report shop status and flag any analytical challenges. Friday: week summary, product archiving, identify what needs to be handed off for weekend coverage. Persistent overlay: deployment readiness, UGT (upgrade training) for junior analysts, additional duties.

The craftsman-level skill that separates good SSgts from mediocre ones is the ability to scope an analytical question correctly. 'What is the threat in this area?' is not an analytical question. 'What is the probability that this specific adversary air defense system can engage our package on this specific route segment given current collection coverage?' is an analytical question. Learning to translate vague operational questions into specific analytical ones — and then answering them honestly — is the core SSgt skill. You also need to be developing your subordinates' understanding of this. It does not come naturally to most people.

NASIC (National Air and Space Intelligence Center) threat products — these are the authoritative assessments for air and space threats and you should be reading them against your AOR reporting to identify where they align and where they diverge. The DIA's DIE (Defense Intelligence Enterprise) products relevant to your region. Your MAJCOM's intelligence directorate products — they are seeing the theater-level picture you may not have visibility on at wing level. Air Force Intelligence, Surveillance, and Reconnaissance Agency (AFISRA) publications. The applicable OPLAN and CONPLAN annexes at the SECRET level — you should have the full version memorized by now.

SSgt-level products are reviewed by the NCOIC or officer-in-charge, but the review is for senior-level polish and policy compliance, not for analytical substance. The craftsman standard is: your products should require only minor revision, your briefings should run without support from a senior analyst, and your junior analysts should be improving under your supervision. If you are still getting products sent back for substantive analytical revision at this level, something went wrong in your development.

The craftsman-level tech mistake is analytical overconfidence enabled by tool familiarity. You know the systems well enough now to produce polished-looking products quickly. Polished presentation can disguise analytical weakness — both from your seniors and from yourself. The other mistake: letting DCGS-AF or your CPOF automation make analytical judgments for you. Those systems are force multipliers for human analysis, not replacements for it. When the system presents a pattern, your job is to ask whether the pattern is real or whether the collection architecture is producing the appearance of a pattern.

The SSgt decision point is the SNCO path. Are you building toward TSgt, which means taking on more supervisory responsibility? Or are you finding that you want to stay in the analytical deep end and seek out special duty assignments — HUMINT exploitation, targeting, national-level intelligence positions? The career field has viable paths in both directions. The mistake is drifting without choosing — doing the minimum supervision required while waiting for something interesting to come along. Make a decision and build toward it.

At the SSgt level, the AOC (Air Operations Center) becomes an option. It is a different experience than the wing — you are working at the campaign level, seeing how intel integrates across all the functional areas of the joint force, and you are producing for a much broader range of customers simultaneously. The tradeoff: you lose the direct relationship with aircrew that gives wing-level intel its feedback loop. Joint assignments at DIA, NGA, or NSA are also possible and valuable for your development, but they pull you away from the operational rhythm that keeps your skills sharp.

A good SSgt-level 1N4 runs the intel shop on a shift without the NCOIC being present and nothing falls through the cracks. Their junior analysts produce better work under their supervision than they did before. Their pre-mission briefs have a reputation with aircrew as being worth paying attention to — not because they are polished, but because they are right. Good looks like: a pilot comes back from a mission and says the threat picture was exactly where your brief said it would be. That is the standard. The other version of good: the pilot comes back and says 'the threat was different than you expected, here is what I saw,' and your shop updates the assessment within hours. That responsiveness is also the standard.

TSgt is the superintendent level. The promotion board is looking for evidence that you can run a flight or section, not just a shift. Your EPRs need to show supervisory impact — analysts you developed, production you improved, processes you changed. Start positioning yourself now. If you are not currently writing bullets about how the shop changed because of you, have a conversation with your rater.