I didn’t ask to be put in charge of the BRITE project. In fact, given a choice I almost certainly would have declined. The odd little system looked distinctly underwhelming—and promised to be a blip on my radar, a forgettable job to be passed off to someone else as soon as possible.

Boy was I wrong. My work on the Broadcast-Request Imagery Technology Environment—a system for sending satellite imagery to troops on the ground—changed my thinking about how we develop military gear.

Bottom line, new weaponry doesn’t have to be expensive. It doesn’t have to involve thousands of people and take years or decades to design.

It was 2002. The war in Afghanistan was new, the invasion of Iraq was still in the future and I was a young Air Force captain assigned to the National Imagery and Mapping Agency.

I already had a day job developing a large communication system, but when BRITE’s previous program manager moved on, somebody had to pick up the baton. I was that somebody … and BRITE became the latest additional duty on my growing list.

I’m embarrassed to say it felt mildly insulting to be handed this task, maybe even a bit of a demotion, because the project seemed so minor and unimportant. The foolishness of that initial reaction dissipated quickly as BRITE saved lives and changed my life.

What was BRITE? The 2004 National Defense Authorization Act described it as “a unique capability to disseminate timely, tailored imagery products … to forward deployed tactical military forces.” The authorization went on to note “Special Operations Forces and others” used the system in Iraq and Afghanistan.

My annual performance report provides more detail, including the fact that we delivered “quality imagery in three minutes versus hours [or] days.” Back then, computers were slower and bandwidth harder to come by, so delivering a large file in a few minutes was considered quite speedy, particularly if the guy on the other end was a special ops troop in an austere location and not some analyst sitting in an air-conditioned building.

I fell in love with BRITE almost immediately. As a military technologist, most of my career to that point had been oriented towards developing tools for a distant future, so it was exciting to have a project that provided an immediate impact.

The fact that BRITE directly supported actual operations overseas was awesome. I also enjoyed the experience of being in charge. As the lead government guy, I called the shots, made the decisions and worked directly with both the developer and the troops.

This was a rare opportunity for a junior acquisitions officer.

All the same, it’s a bit of a stretch to say I was “in charge” of the project—because I had no budget to speak of and no staff whatsoever. I was really only in charge of myself.

Fortunately, I was not alone in my aloneness—the small defense contractor that built BRITE had assigned one guy to work it, also part-time. John had as many other duties as I did, but like me, this was his favorite.

Our main customer in those early days was special operator who went by the call sign “Scrounger.” He was an inventive and enthusiastic guy who made BRITE do things John and I never imagined.

Several of the innovations we delivered were a direct result of his feedback from the front lines. My performance report for 2003 notes that BRITE “was critical in prisoner recovery operations” and quotes an unnamed special ops soldier—spoiler alert, it was Scrounger—as saying “it’s like magic.”

The kind words about BRITE’s magical performance may have shown up on my record, but Scrounger waved the wand and deserves most of the credit.

Not everyone loved our program the way John, Scrounger and I did. Specifically, the budgeteers had a tendency to leave it out of their accounting spreadsheets. In fact, the aforementioned authorization act complains that “despite the urging of the Congress, NIMA failed to include funding for BRITE” in its proposed budget three years in a row.

Congress earmarked money for BRITE each year, anyway, which gave me a whole different perspective on news reports about the legislative branch funding programs the military didn’t ask for.

Interestingly, the funds I remember receiving through these budgetary plus-ups is much smaller than the amounts identified in the legislation. I seem to recall a conversation or two in which objections were raised about BRITE being shortchanged, but we were told NIMA’s decision to spend the dollars elsewhere was necessary and appropriate. I’m sure it was.

Of course, the green-eyeshade crew was only following orders from the people higher up in the agency. One day, as I was on my way back from a meeting, my boss stopped me in the hallway to let me know some bad news. “They tell me I should cancel BRITE,” he explained, “because it’s making the larger programs look bad by doing so much good for so little money.”

He grinned as he continued. “But don’t worry. I’m an old man and my hearing’s not what it used to be. You keep up the great work and I’ll keep the vultures away.”

That’s not a conversation—or a leader—one quickly forgets.

At that point in my career I was just starting to understand the defense technology business and to formulate opinions as to what constituted a good system. Working on BRITE challenged my previous assumptions about the value of large, expensive development programs … and showed me the wisdom of going small.

Long before Defense Secretary Robert Gates said that “the best solution isn’t always the fanciest or the most expensive,” I got to live this important truth.

BRITE brought innovative, first-in-class, best-in-class capabilities to the pointy end of the spear, helped with the first prisoner-of-war recovery effort since the Vietnam War and did it all with a skeleton crew and a shoestring budget.

It proved that top-shelf technology can support operations at the speed of need without consuming vast resources. It showed the importance of deliberately pursuing elegant simplicity in both the technical design and the organizational structure supporting that design. It set the foundation for much of my later work in the area of rapid, low-cost innovation, both as an engineer and a writer.

It also destroyed my ability to contentedly work on a large, expensive, complex program designed to address a far-off, hypothetical need. For that, I am deeply thankful.

Speaking of expensive programs, BRITE was a stark contrast to one of my other duties, the infamous Future Imagery Architecture program, which I worked on for about a year. FIA was terminated in 2005 due to significant delays and cost overruns.

The specifics are still classified, but The New York Times reported that the cost was upwards of $18 billion, a number I can neither confirm nor deny.

It is a bit generous to say I “worked” on FIA. Mostly I was dragged to endless meetings where I listened to people debate whether the previous week’s meetings had resolved some obscure issue—they hadn’t—and whether the current meeting should be considered a technical interchange meeting or a technical exchange meeting.

Because if it was a TEM, we clearly did not have the right participants in the room and thus would need to reschedule. I wish I were making that up.

I soon figured out a way to stop going to those pointless meetings, but nevertheless my annual performance report praised my work on the “security accreditation plan for Future Imagery Architecture” which was apparently “lauded by seniors.”

The two programs could not have been more different. BRITE was simple, focused and effective. It provided actual users with combat-relevant capabilities that were previously unavailable, such as overlaying signals intelligence and Blue Force Tracking data onto minutes-old high-resolution satellite imagery—and it did so with minimal overhead.

Along with serving well in Iraq and Afghanistan, it went on to support security efforts for the Olympics. It was the very definition of a successful technology innovation. Naturally, this is the program certain mid-level managers wanted to cancel and refused to fund.