Designing a Community Hub With R&D, Not Over the Wall

A community hub looks simple from the outside and is full of quiet complexity underneath — events with state, interest-based connections, notices, courses, and benefits all sharing one home. On Shibolet's internal platform I was the solo designer, which meant my relationship with R&D wasn't a handoff at the end; it was a continuous conversation from the first flows onward. What I learned to bring engineering early was intent, not just pixels. When I proposed surfacing community activity alongside formal firm content, the meaningful questions were technical: how do these content types relate, what's the data model behind a connection or an event, what's genuinely reusable across the roughly ten flows. Talking through those constraints with R&D shaped the design itself. I'd rather adjust a layout to fit a sane component model than ask engineering to contort the architecture for a flourish that doesn't earn it. For an engineering leader, the payoff is predictability. Because we agreed on shared building blocks and consistent patterns up front, the social and corporate sides of the hub could share one coherent system rather than becoming two divergent codebases. Collaboration kept the warmth in the product without scattering it across the stack.