Project ONE
Team Lipi · The what

Team Lipi

Lipi (लिपि) is Sanskrit for script.

The Requirements Engine — WHAT to build

Team Lipi decides what Venus needs to build. Project Elevate builds it. Together, they carry Project ONE's vision.

The one question

What should Venus build?

Gap

The gap it closes.

The same organization, with and without a place that decides what gets built.

Without Team Lipi

  • Random experimentation without strategic coherence
  • Departments building tools disconnected from the vision
  • Wasted effort on low-impact projects
  • No learning transfer across departments
  • Technology adoption without transformation

With Team Lipi

  • Strategic filter for what gets built
  • Requirements tied to Project ONE
  • Cross-functional learning and pattern sharing
  • Distributed strategic thinking, not just top-down
  • Clear roadmap feeding Project Elevate's execution
Questions

Six mission questions.

Every session starts from these.

  1. 01

    “What work should go to AI?”

    Find the routine, pattern-based work AI can handle.

    e.g. Quality report generation: AI-assisted

  2. 02

    “What work requires human + AI collaboration?”

    Complex analysis where AI amplifies human judgment.

    e.g. Root cause analysis: AI surfaces patterns, humans judge validity

  3. 03

    “What work must remain purely human?”

    Relational, judgment-based, and tacit knowledge work.

    e.g. Mentoring, culture-building, and ethical decisions stay human

  4. 04

    “What new skills do people need?”

    Capability gaps in the AI-enabled future.

    e.g. Manufacturing supervisors need AI prompt engineering skills

  5. 05

    “What new workflows are required?”

    Process redesign for AI-human collaboration.

    e.g. Deviation workflow redesigned with AI pre-screening

  6. 06

    “What exactly should Venus build?”

    Specific software, tools, and capabilities Venus needs.

    e.g. Build AI-powered batch record analyzer by Q3

Layers

Three layers of work.

Where the work goes, and what a person still holds in each.

  1. Layer 1

    AI-Delegated Work

    Pattern matching, routine cognition and information processing. AI does the work; a person oversees it.

    • Regulatory report generation from data
    • Routine documentation and record-keeping
    • Trend analysis in batch records

    Human role Set parameters and validate outputs

  2. Layer 2

    Human + AI Collaborative Work

    Complex analysis that needs computational power and human judgment together.

    • Root cause analysis: AI correlations + human causation
    • Quality investigations: AI patterns + human judgment
    • Process optimization: AI modeling + human know-how

    Human role Strategic thinking, contextual judgment, and synthesis

  3. Layer 3

    Purely Human Work

    Relational, emotional and tacit work — ambiguity only people can navigate.

    • Building psychological safety in teams
    • Navigating regulatory gray areas
    • Mentoring, culture-building, and ethical judgment calls

    Human role Wisdom, presence, connection, and discernment

Skills

Critical skills.

The ones that can't be handed to AI.

  1. Emotional Clarity

    Understanding emotions without being run by them. Deciding from awareness, not reaction — critical in high-stakes pharmaceutical calls.

  2. Discernment

    Seeing clearly amid complexity. Finding the signal and cutting to what matters.

  3. Connection

    Building psychological safety through the VIEW framework — Vulnerability, Impartiality, Empathy, and Wonder. Teams that connect share problems earlier.

  4. Contextual Intelligence

    Pattern recognition specific to Venus. Knowing what works here, not just in theory — business is probabilistic, not physics.

How

How it works.

Structure
Volunteers: 8–12 self-selected people who meet monthly to decide what Venus should build.
Outputs
Each quarter, a prioritized roadmap of requirements, handed straight to Project Elevate.
Cycle
The six mission questions frame every session. Each takes on one or more and turns the vision into specific, buildable requirements.