Luma LabLuma LabWashington, DC

Inclusive Innovation

Why DC Needs Inclusive Tech Spaces

Washington has no shortage of technology work. It has federal contracts, a dense consulting sector, universities running computer science departments, and a startup scene that has been growing for two decades. What it has unevenly is access to that economy, and the unevenness follows the city's geography with uncomfortable precision. This is an argument for why the answer to that has to include real rooms in real neighbourhoods, and what those rooms have to contain to be worth anything.

Luma Lab · August 4, 2026 · 4 min read

The gap is geographic before it is technical

The most common framing of the technology access problem is a skills gap, which implies that the missing ingredient is instruction. Instruction is necessary and it is not the binding constraint. A resident of Ward 7 or Ward 8 who wants to learn to write software faces a set of obstacles that arrive well before any curriculum does, and most of them are about distance.

Washington's technology employment and its co-working infrastructure cluster in the city's northwest quadrant and along the corridors that serve it. Getting from east of the Anacostia to those addresses is not impossible, but it is a transfer-heavy trip that eats an evening, costs fare in both directions, and does not work at all for someone with a shift that ends at six or a child to collect. A free evening class held somewhere unreachable is functionally not free.

Which is why the location of a program is a curriculum decision, not a logistics decision. Where a room is determines who can be in it.

What an inclusive space actually provides

The phrase inclusive innovation gets used loosely enough that it is worth being concrete about what the physical space has to deliver. A space that only offers desks and enthusiasm is a co-working membership with better marketing. The things that change outcomes are unglamorous and mostly logistical.

The provisions that separate a working space from a branded one:

  • Hardware that stays on site, so participation does not require owning a laptop
  • Connectivity fast and stable enough for video calls, package installs, and interviews
  • Hours that extend past the end of a work shift and cover weekends, not just business hours
  • Staff physically present who can unblock someone, rather than a badge-access room with nobody in it
  • Space where a parent can bring a child without it being a problem
  • A mailing address and a room with a door, for someone registering a business or taking a client call

Why proximity to a university matters

Placing a community technology space next to a university changes what it can do, in both directions. Students gain somewhere to work on projects that are not coursework and to meet people who are building things outside the academic calendar. The neighbourhood gains proximity to a research library, to faculty, to visiting speakers, and to the informal network effects that make a campus useful to people who are not enrolled.

The Georgia Avenue corridor around Howard University is a specific example of this working. It is a residential and commercial corridor with a major research university sitting inside it rather than walled off from it, on a Metro line, in a part of the city where a technology space is not otherwise a given. A room there is reachable by people who live nearby and by people who study nearby, and those are not the same population.

The failure mode to avoid is the space that treats the campus as its market and the neighbourhood as its backdrop. If the room fills exclusively with enrolled students, it has become a study hall with sponsorship, and the reason it was placed there has quietly stopped being true.

Measuring whether a space is working

Attendance is the metric everyone reports because it is the easiest to collect and the most flattering. It is also close to meaningless on its own. A launch event fills a room; so does free food. Neither tells you whether anybody learned anything or came back.

The measures worth tracking are about return and progression. What share of first-time attendees come to a second session. How many participants start a second project after finishing a first one. How many people who came in for a class end up using the space independently for their own work. How many stay in contact after a program ends. Those numbers are smaller, less impressive in a press release, and considerably more honest about whether the room is doing its job.

They also fail usefully. A space with strong first-visit numbers and weak return numbers has a specific, fixable problem, usually in scheduling, transport, or the first-session experience. A headcount total tells you nothing you can act on.

How local partners keep programs alive

No single funding source sustains this kind of work for long. Government grants are lumpy and tied to political cycles. Corporate sponsorship follows corporate priorities and arrives in bursts around announcements. Foundation money is usually project-scoped and does not cover the operating cost of keeping a door open on a Saturday. A program that depends on any one of those is a program with an expiry date it does not know about yet.

The durable arrangements mix them, and pair each funding stream with a partner who supplies something other than money. Schools supply students and a reason for parents to trust the program. Community organisations supply the trust itself, which cannot be bought or built quickly. Employers supply mentors, equipment that has rotated out of their fleet, and a plausible destination for participants who finish. Universities supply space, faculty, and credibility with funders.

That is a slower way to build than raising one large grant, and it is the reason some of these spaces survive a change of administration and others do not. A program held up by six relationships loses one and keeps running. A program held up by one loses it and closes.

More from the lab

All articles