Maya kept a page called “What We Learned.” It was a short distillation: numbers tell how systems behave; stories explain why they matter; solutions are seldom one-size-fits-all. She also kept a simple editorial principle at the top of the About page: clarity over cleverness; people over metrics.
The turning point came when a city council member in a mid-sized town read a piece about small revenue innovations and reached out. She asked if Maya could prepare a clear memo for a series of local meetings—practical options for raising funds without burdening low-income residents. Maya synthesized several FSIBlog posts into a single briefing, added a few local examples, and sent it off. The council adopted one pilot idea: a sliding-fee permit system for commercial events. It wasn’t a miracle fix, but the pilot reduced administrative friction and funded a youth summer program the next year. The council member credited the accessible analysis she’d found on FSIBlog. fsiblog page
FSIBlog’s aesthetic evolved with purpose. The design stayed minimal—clean typography, lots of white space—but Maya introduced small data visuals: annotated bar charts, simplified flow diagrams, and micro-interviews boxed into the margins. Each visual answered one question clearly, the way a post should. The navigation bar gained tags: “Household,” “Policy,” “Startups,” “Reader Stories,” and “Explainers.” Every tag aimed to guide curiosity, not to trap readers in jargon. Maya kept a page called “What We Learned