proomt

Search

Search posts, papers, and topics

All posts

ThoughtbotMariia Sus3 min readintro

From In-House PM to Consulting PM: What I Didn't Expect

Summary

The author describes how moving from an in‑house PM role to a consulting one stripped away direct access and authority, forcing a shift toward influence, context‑gathering, and enabling the client team rather than executing decisions herself.

  • You must explicitly identify who owns information and formally request it, since you no longer have direct access to internal teams or data.
  • Influence replaces authority: build trust, present reasoned recommendations, and let the client own decisions.
  • Slow approvals often hide multi‑layered processes or overloaded teams—uncover this context before judging speed.
  • Stop doing everything yourself; facilitate discussions, surface risks, and help the client make better decisions.

Product managers and consultants should read this to understand how to adapt their influence and decision‑making style when moving from internal to client‑facing roles.

5/10

Related reading

  1. Article: Beyond Relevance: A Governance-First Architecture for Enterprise Personalization

    The article proposes a governance‑first architecture for enterprise personalization, where policy‑driven steps (memory, journey graph, AI routing, scoring, trust checks, outcome simulation) shape the recommendation before it is returned. A reference FastAPI implementation demonstrates the pattern with external YAML policies and optional LLM assistance.

    InfoQinfoq.com19 min
  2. Presentation: Context Engineering at LinkedIn: How We Built an Organizational Context Layer for AI Agents with MCP

    LinkedIn built a “Contextual Agent Playbooks and Tools” layer that wraps internal services (code search, docs, feature flags, etc.) behind the open‑source Model Context Protocol (MCP). By feeding LLM‑powered coding agents the exact internal artifacts they need, the agents can diagnose incidents, generate PRs, and update incident tickets in minutes, delivering a reported 20 % productivity gain wit…

    InfoQinfoq.com28 mintalk
  3. What Sun got wrong

    The author reflects on Sun Microsystems, arguing that despite strong technology, Sun failed because it grew bored with the mechanics of running a business—illustrated by a 2005 startup’s experience where Sun’s sales response was slow and mismatched while Dell’s personal rep closed the deal quickly. The story warns engineers and founders that operational discipline is as critical as technical visi…

    Lobstersdtrace.org3 minHN478263lobste.rs86
  4. System Design Interviews for Data Roles: What to Actually Practice

    The piece shows that data‑role system design interviews evaluate how you turn vague requirements into a defensible architecture, not which tools you name, and it gives a concrete prep framework: clarify scope, quantify load, pick batch vs streaming with trade‑offs, and address failure handling. Candidates should rehearse explaining these decisions aloud with numbers rather than just drawing diagr…

    SitePointsitepoint.com6 min
  5. Article: Your Next DSL Author Is a Language Model

    Typed Domain Grounding (TDG) embeds a DSL inside a mainstream language the LLM already knows (e.g., Kotlin) and uses the host compiler as an oracle. The author describes five building blocks—embedding, choosing a host language with high training‑data frequency, compiler‑driven type safety, a generate‑compile‑repair loop, and an on‑demand teaching tool—and shows measured results from kUML, a Kotli…

    InfoQinfoq.com18 min