Skip to main content
Meytal Dahan
Back to insights

Why I Didn't Reach for AI Here

Shibolet & Co. — Designed the firm's internal community hub - balancing the gravitas of a top legal practice with a social tone inviting enough that employees would actually use it - into a space precise enough to belong inside the firm and warm enough to feel lived-in.
The founder instinct right now is to lead with AI, so let me be honest about a project where the strategic call was restraint. Shibolet & Co.'s hub was a digital community for a leading law firm's employees — benefits, courses, notices alongside events and interest-based connections. The temptation is obvious: surface AI-driven recommendations, auto-match people by interest, generate content. But the actual problem wasn't a shortage of intelligence; it was a shortage of warmth and reasons to show up. In a legal environment, trust and discretion are the culture, and a heavy-handed algorithm guessing who you should befriend reads as the opposite of warm. So my AI strategy was a posture, not a feature dump: the smartest move was earning engagement through human-centered design first, and treating any future automation — surfacing relevant events, nudging interest-based connections — as something that enhances a hub people already trust, never a substitute for the editorial and social judgment that makes a community feel human. Founders fund vision; the disciplined version of an AI strategy is knowing where intelligence genuinely serves the user and where it would erode the very trust the product depends on. Here, the strategy was to keep the foundation human and let AI earn its way in later.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Shibolet & Co.
Engineering LeadersProject-Specific Data Visualization

Visualizing a Community, Not a Dashboard

Say data visualization to engineers and they picture analytics dashboards. Shibolet's internal community hub needed the opposite. It was a community hub for a law firm, not an admin reporting tool. The job was making events, courses, benefits, and interest groups scannable and inviting, with light cues like who's attending or active. No charting engine, no KPI grid. Project-specific data viz means the representation answers this domain's real question. Here it was always: what's happening in my community, and what's for me?

Read
Shibolet & Co.
Project Managers

Running a Digital Project in a Legal Organization: How Do You Hit Deadlines When Partners' Time Is Worth Gold?

Project Managers in legal organizations — your biggest pain point is the billable hours of your partners. On the Shibolet & Co. project we developed a "Batched Approvals" method paired with Figma prototypes: every decision is presented with 3 clear alternatives, and a partner can sign off in 15 minutes instead of an hour. That's how you protect the Gantt and the budget.

Read
Shibolet & Co.
Product ManagersTypography & Visual Hierarchy

Typography as Triage: Ordering a Legal Community Hub

PMs keep asking: how do users know what matters when one screen does five jobs? On Shibolet's internal hub, a single view carried a compliance notice, a new course, a firm event, and a community invite. I didn't solve that with more tabs. I solved it with typography. A deliberate type ramp let official items read with authority and social content stay warm, in the same layout. Visual hierarchy is product triage made visible. Get the type ramp right and you stop negotiating screen real estate per stakeholder.

Read
Meytal Dahan

About

Making complicated into easy for users.

Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.