Leveling Up: A Wiki-Based Tactics, Techniques, and Procedures System for a Modern Air Force

By: Maj Matthew K. Pardini

US Soldiers from 1st Platoon, Bravo Battery, 1-377 Field Artillery Regiment,17th Fires Brigade, conduct counter indirect fire patrols through neighborhoods around Basra, Iraq, March 18, 2010. The frequent patrols by US and Iraqi Soldiers disrupt possible insurgent attacks on Contingency Operating Base Basra. (Photo by Staff Sgt. Adelita Mead)

Abstract

This article promotes using a dynamic, web-based wiki system instead of static publications for Air Force Tactics, Techniques, and Procedures (TTPs). The article recognizes the limitations of current TTP update processes, which are slow and reliant on limited subject matter experts. It proposes a wiki platform to enhance accessibility, collaboration, and real-time information sharing. The article explores the benefits of wiki formatting, including enhanced accessibility and usability, improved collaboration and updating, cost and resource efficiency, and enhanced security and control. The article includes a model of a user-centered implementation approach, emphasizing streamlined editing, rigorous review processes, and continuous feedback. The article addresses potential challenges, such as resistance to change and security concerns, with practical mitigation strategies. The Air Force can ensure Airmen have access to the most current and accurate information by adopting a wiki-based TTP system, fostering agility and continuous improvement in an ever-evolving operational environment.

Introduction

The ability to adapt and respond rapidly to evolving threats is paramount in the modern Air Force. The current and future dynamic logistics environment demands our units operate with unprecedented speed and flexibility, often in distributed and contested environments. This necessitates a change in basic assumptions in managing and disseminating critical information, particularly . While our current TTP publications contain valuable knowledge, their static nature can hinder our ability to maintain operational relevance in a world of constant change. To illustrate the critical need for dynamic information sharing, consider a simple lesson learned from a challenging deployment.

Staff Sgt. David Melton, 723d Aircraft Maintenance Squadron (AMXS) crew chief, reads a technical order, May 15, 2018, at Moody Air Force Base, Ga. Airmen from the 723d AMXS along with machinists from the Corpus Christi Army Depot conducted a full structural teardown and restoration on an HH-60G Pave Hawk. Once the aircraft was torn down, Airmen and the machinists performed repairs on all of its components prior to resembling it. (US Air Force photo by Airman 1st Class Eugene Oliver)

Before transitioning to be an Aircraft Maintenance Officer, I had the tremendous opportunity to support and document missions across the DoD as a combat videographer. This experience provided unique insights into operational realities. During a deployment to Iraq with the US Army, most of our days involved nighttime apprehension missions, requiring our team to navigate challenging terrain far from established forward operating bases. Often, these operations included dismounted movement several kilometers into local villages to locate the designated person of interest. The environment presented numerous obstacles, from unpaved roads to crossing fields and irrigation channels. To avoid unnecessary injuries or delays, we developed a simple, yet effective, technique to identify hazards. When we encountered potholes, rough patches, etc., we communicated the hazard to the team member behind us by whispering a verbal warning, “hole” or “lookout” with a quick lasso of our Infrared (IR) laser, visible under night vision goggles, to highlight the hazard until acknowledged by the following team member. This simple method worked perfectly to keep us on track and moving forward.

This experience underscored the importance of clear communication and shared situational awareness in dynamic, contested environments. Much like this simple tactic, Air Force TTPs identify and communicate potential hazards or challenges to those who follow. By leveraging lessons learned from past operations and disseminating them effectively, we can enhance the preparedness and agility of our units, particularly in the context of Agile Combat Employment and distributed operations.

Our Air Force TTPs contain a wealth of valuable and relevant information. However, the updating process moves a lot slower than a quick lasso of an IR laser. It is more akin to an Army team relying on unbelievably detailed maps that include ground debris and obstacles that are only updated every two years. The maps are initially effective but quickly outdated after a few days of heavy traffic. Air Force TTPs need a more dynamic updating process that ensures changes happen at the speed of relevancy and encourages Logisticians to check it and contribute to it often.

TTP publications are essential for the Air Force, providing critical guidance and standardization across various operations. Traditionally, these publications are distributed in static formats, such as printed manuals or PDFs. However, with the rapid advancement of technology, it is time to consider a more dynamic and efficient approach. My solution to this problem is to adopt a web-based wiki platform that can be seamlessly integrated with our existing systems and is accessible to anyone with Common Access Card (CAC) access (and SIPRNet access for classified TTPs). This integration will ensure that Logisticians can access updated TTPs with edits scrutinized by experts across the globe, complete with hyperlinks to related procedures and Department of the Air Force Instructions (DAFIs). Seamless access to the latest information ensures we stay dynamic and relevant, enhancing mission readiness.

Popularized by platforms like Wikipedia, Wiki formatting offers a collaborative, web-based system for creating and managing content. This article explores the numerous benefits of transitioning TTPs to a wiki format and outlines a strategic approach for implementation.

Benefits of Wiki Formatting for TTP Publications

Static TTP publications lack the ability to improve collaboration and update with relevance. As we approached last year’s Flying Hour Program (FHP) First Look, I noticed Misawa’s Fighter Generation Squadrons (FGS) are using a Heath Information Tool (HIT) Model in addition to the ACC-mandated Sortie utilization (SUTE) model to quantify our FHP capabilities better. Imagine you are a new FGS Director of Operations (DO) building your first FHP, and the SUTE model is not capturing everything you read in Chapter 4 of the TTP that you must consider. The SUTE model is also not adding up to what you see as your everyday capability, so you go to your wiki-formatted TTP and notice Misawa added a hyperlink to the HIT Model for you to use and rerun your numbers to verify the SUTE model or give you better planning factors as you build your FHP.

Image courtesy of Shutterstock. (Photo contributor Antlii)

Enhanced Accessibility and Usability

The days of only Commanders having iPhones with Blackberry Unified Endpoint Management Client access have changed, and many DOs, Aircraft Maintenance Unit Officers-in-Charge (OICs), and Production Staffs are starting to use iPads to brief aircraft status, Health of Fleet briefings, and pre-deployments. Having wiki-based TTPs at their fingertips can easily ensure credibility as they brief senior leaders. As long as they have an internet connection, they can retrieve information anytime and almost anywhere.

Additionally, the ability to hyperlink related topics within the wiki enhances the interconnectedness of information, allowing users to explore relevant content seamlessly. Think of it as a web of knowledge where each link takes you deeper into the subject matter.

Improved Collaboration and Updating

Unlike static documents, wikis allow fast updates and corrections, ensuring the most current information is always available. This faster update method also encourages Logisticians to check the TTPs more often to ensure the best way has not improved. In addition to timely and relevant TTP updates, multiple contributors can work on the same document simultaneously, fostering a collaborative environment integrating expertise from various sources.[i] It is like having a team of experts from across the Air Force in one room, each adding their knowledge to create a guide that best serves the mission.

The benefit of version control is that a wiki publication provides content integrity.[ii] Wikis can maintain a history of changes, allowing users to track edits and TTP Model Managers to revert to previous versions if necessary. This is like having a time machine for your documents, not afforded by static TTPs. You can see how they evolved and potentially revive an outdated TTP as some fleets age.

Cost and Resource Efficiency

In an era of slashing budgets, reducing costs while not decreasing lethality is always desired. Transitioning to a digital format eliminates the need for paper copies, significantly reducing printing and distribution costs. In addition to printing cost savings, managing TTP content in a wiki is more straightforward and less resource-intensive than maintaining static documents. I will discuss the current TTP updating process later. However, eliminating the requirement of getting everyone together for one week at Nellis AFB saves time and allows for more time to make relevant and lasting changes.

Wiki publications increase resource efficiency because wikis can easily accommodate new topics and updates, making them a scalable solution for the Air Force’s evolving needs. This ability to scale as needed can help the Air Force realize substantial cost savings, optimize personnel utilization, and ensure access to the most up-to-date information to increase mission effectiveness.[iii]

Enhanced Security and Control

Wikis can be configured to allow anyone with access to edit the content, but a completely open editing approach would not be suitable for something as critical as Air Force TTPs. Instead, TTPs wikis can include a moderation process requiring approval from the Advanced Maintenance and Munitions Operations School (AMMOS) Model Manager or a designated TTP review board, which would strictly control publishing changes to ensure all updates are vetted for accuracy and adherence to Air Force standards before publication.

A wiki-based system does not equate to an “anything goes” approach. Instead, wiki publications can allow the ability to monitor changes and contributions to provide accountability and transparency.[iv] This ability to review before publishing is akin to having a Consolidated Tool Kit Support Airman checking to ensure the 10mm socket is in the tool kit before checkout. The meticulous examination of every TTP edit and addition ensures accuracy and prevents the loss or alteration of critical information, effectively maintaining a system of checks and balances.

Image courtesy of Shutterstock. (Photo contributor KristinaWv)

Limited Updates: The TTP Update Process

I got to be a part of the process to update the Aircraft Maintenance TTPs in 2022. While it was the best method to update our TTPs, it was cumbersome and relied heavily on a limited pool of Subject Matter Experts (SMEs). It began with AMMOS emailing the 21X graduate network and soliciting volunteers to revise specific chapters or attachments. Graduates could also submit the desired updates, particularly if they were unable to attend the rewrite conference or their area of expertise was already assigned.

Prior to the conference, AMMOS distributed a TTP draft to the selected SMEs for review. SMEs focused on identifying content gaps, redundancies, and inconsistencies and assessing relevance and value. They could also collaborate with other SMEs within their units or networks for additional input.

The actual rewrite conference required SMEs to physically travel to the AMMOS schoolhouse, at unit expense. Unfortunately, this funding constraint limited participation. During the week-long conference, SMEs convened at the 423rd Maintenance Training Squadron TTP building. While this facilitated valuable collaboration and discussion, the in-person requirement remained a barrier for many to attend.

After all the planned and impromptu discussions ended and the subsequent section rewrites and edits were completed, the SMEs returned to their units, and the process concluded with a final review by the Model Manager. After several months and a couple of layers of approval, the updated TTPs were released.

Despite the best intentions, the Aircraft Maintenance TTP update process, while offering a platform for improvement, suffers from several key limitations. The reliance on a volunteer-based SME pool, solicited through a limited graduate network, inherently narrowed the scope of expertise and potential for diverse input. While pre-conference draft reviews allowed for asynchronous feedback, physical attendance at the AMMOS Schoolhouse and unit-funded travel presented a significant barrier, potentially excluding valuable SMEs. This centralized, time-intensive approach, culminating in a lengthy post-conference review and approval process, ultimately hinders the agility and timeliness of crucial TTP updates.

Shaping the Wiki TTP: A User’s Perspective

A wiki-based TTP implementation strategy is an entire article on its own, so I will skip that step and explain what I envision the process looking like for the tactical-level Airman updating the future wiki-based TTP and the steps the AMMOS Schoolhouse plays in it.

To start editing an existing chapter or section of the TTP, users would simply navigate to the TTP wiki page they want to update and click the “Edit” link. This link opens the article in an editing window where they can make changes directly to the text. Users can include references listing AFIs, books, other TTPs, etc. In addition to making edits to already included content, users can add new chapters or attachments using these same steps. When users finish editing, they must write a short “edit summary” describing the changes before submitting to help the AMMOS Schoolhouse understand the intention of the edit and source SMEs to review the changes, if required.

Whether the changes are added content or edits to previous content, they will not take effect immediately. All changes must be reviewed by the AMMOS Schoolhouse or designated TTP managers (SMEs from that field) to ensure TTP credibility and formatting for ease of use.

The last step in the process is ensuring the AMMOS Schoolhouse gets feedback from users in the field. Collecting user feedback during the first year will provide valuable insights for making necessary adjustments. Hopefully, the user feedback will be parallel to the straightforward and sometimes harsh cadre debriefing after an AMMOS exercise.

Potential Challenges

As with any change, I acknowledge transitioning to a new system can be met with resistance. President Bill Clinton said it best when he stated, “The price of doing the same old thing is far higher than the price of change.” Changing from static TTPs to a dynamic wiki publication requires buy-in from maintenance leadership and Wing Patches (AMMOS graduates) to advocate for and use the new system. Moreover, Wing Patches should communicate the benefits of a wiki-based system and emphasize how it addresses the shortcomings of the current process and directly supports mission effectiveness. Additionally, hands-on demonstrations within all units will showcase the wiki’s capabilities and help users better understand the power of a recently and constantly updated TTP. Finally, we could consider recognizing and rewarding early adopters and top contributors to foster a culture of engagement.

Publishing maintenance TTPs online is not a concern in a world where almost every Air Force system we use is already online. Security relies on the wiki TTPs hosted on a secure government network, such as NIPRNet, with access restricted to authorized personnel via CAC authentication. Specifically, all data, including revisions and user activity logs, should be encrypted both in transit and at rest to prevent unauthorized access.

The last potential objection the field could have is who the change reviewers are and who gives the final approval before publishing changes. To avoid issues with false information being added to the TTPs, different reviewer and approver rights must be given to users across the Air Force. While anyone with CAC access can submit changes, authorized reviewers should be limited to Wing Patches, O-5 and above 21Xs, and AMMOS. In contrast, approval rights are limited to the TTP Managers and AMMOS leadership. Additionally, no one can review their own entry to ensure objectivity. While these different reviewer and approver layers make the process less dynamic than instant publication, as we are accustomed to with the popular Wikipedia website, it is still faster than the current two-year process and ensures we are not publishing false information to the field.

AMMOS Grad Patch photo featured on Nellis Air Force Base’s Facebook post. (Image by Airman 1st Class Michael Sanders & Senior Airman Timothy Perish)

Conclusion

Just as my experience in Iraq highlighted the need for real-time communication and shared situational awareness on the battlefield, a wiki-based TTP system empowers Airmen at all levels to access, contribute to, and benefit from a constantly evolving knowledge base. It transcends the limitations of geography, rank, and traditional information silos, fostering a culture of collaboration and continuous improvement.

Transitioning TTP publications to wiki formatting offers numerous benefits, including enhanced accessibility, improved collaboration, and cost efficiency. By adopting this modern approach, the 21X career fields (and potentially the entire Air Force in the future) can ensure that its personnel have access to the most current and accurate information, ultimately enhancing operational effectiveness. Our TTPs are not merely static documents but vital lifelines connecting Airmen to the collective knowledge and experience of the entire force.

By embracing a wiki-based TTP system, the Air Force can enhance mission effectiveness, empower agile decision-making, and foster a culture of innovation. The transition to a wiki-based TTP system is not simply about adopting a new technology; it is about embracing a mindset of agility, collaboration, and continuous learning. In a world where the pace of change is only accelerating, this shift is essential for the Air Force to maintain its competitive edge and ensure mission success in the years to come.

The views expressed in this article are those of the author and do not necessarily reflect the official policy or position of the Air Force, the Department of Defense, or the US Government. 

About the Author

Maj Matthew Pardini currently commands the 35th Maintenance Squadron at Misawa AB. With 25 years of Air Force service, his extensive career spans maintenance, logistics, and broadcast journalism, including deployments to Iraq, Afghanistan, Türkiye, and Southwest Asia. Notably, as an AMMOS instructor, Maj Pardini directly engaged with TTPs, contributing to their revision and understanding of their critical role in operational effectiveness. His experience provided firsthand insight into the challenges of maintaining relevant and up-to-date information, a key factor driving his advocacy for modernizing TTP management through wiki-based platforms. His practical experience in developing and teaching TTPs lends valuable perspective to the article’s exploration of enhancing information dissemination within the Air Force.

Works Cited

[i] Majchrzak, A., Jarvenpaa, S. L., & Hollingshead, A. B. (2016). A knowledge-based perspective on internet-enabled innovation: Activating dispersed knowledge via social computing. Organization Science, 27(6), 1350-1372.

[ii] Wagner, C. (2004). Wiki: A technology for conversational knowledge management and group collaboration. Communications of the Association for Information Systems, 13(1), 265-289.

[iii] Leonardi, P. M., & Contractor, N. S. (2018). Digital work: Research on the social enabling of information technologies. Academy of Management Annals, 12(2), 815-885.

[iv] Schneberger, S. L., & Violino, M. (2021). Governing enterprise wikis: Balancing openness and control. Information & Management, 58(2), 103429.