A tiny shared ritual for the team portal.

The product problem

Internal portals often have news and tools but few lightweight shared rituals. Building a proprietary daily game is far outside most internal-product roadmaps.

Why this placement can work

A common puzzle can create informal conversation without needing employee profiles inside the game. The host can pair it with its own chat or culture program while the embed remains intentionally simple.

Implementation notes

• Place it in a voluntary community or break section, not a mandatory workflow.
• Do not send employee IDs, names or emails in source parameters.
• Use a stable company or portal placement label.
• Keep competitive discussion in the company’s existing collaboration tools.

What to avoid

• Do not use solve times for employee evaluation or monitoring.
• Do not imply participation is required.

A practical example

A distributed team portal has a “Coffee Break” block with today’s two puzzles and a link to the company’s existing social channel for discussion.

Minimal HTML

<iframe
  src="https://puzru.com/embed/?mode=daily&source=intranet-puzzle&theme=auto&surface=card"
  title="Daily logic puzzle"
  loading="lazy"
  sandbox="allow-scripts allow-same-origin allow-popups"
  referrerpolicy="strict-origin-when-cross-origin"
  style="display:block;width:100%;max-width:540px;height:720px;border:0;background:transparent"
></iframe>

The host page should remain genuinely useful without the widget. The embed is an interaction layer, not a reason to manufacture thin pages.