Setting Up Microman for Engineering Teams

Implementing Microman for your engineering team is straightforward, but a few key configuration choices can make the difference between good and transformative results. This guide walks you through the optimal setup process based on our experience with hundreds of engineering teams.

Step 1: Installation

First, install Microman globally:

npm install -g microman

Or using Yarn:

yarn global add microman

Verify the installation:

microman --version

Step 2: Team Configuration

Create a team configuration file:

microman init

This will prompt you for:

• Team name
• Team members (usernames or emails)
• Preferred standup time
• Integration preferences (Slack, Teams, etc.)

The configuration is stored in .micromanrc in your project root. For teams using multiple repositories, you can place this in a shared location and reference it with the --config flag.

Step 3: Customize Update Categories

By default, Microman uses three update categories:

• Completed
• Blocked
• Next Steps

For engineering teams, we recommend adding these custom categories:

{
  "categories": [
    "Completed",
    "Blocked",
    "Code Review Needed",
    "Next Steps"
  ]
}

This helps surface code reviews that might otherwise become hidden blockers.

Step 4: Integration Setup

Microman is most effective when integrated with your existing tools. We recommend:

GitHub/GitLab Integration

microman integrate github --token=YOUR_TOKEN

This allows Microman to:

• Pull recent commits for pre-filling "Completed" items
• Link to PRs that need review
• Track issue status changes

Slack Integration

microman integrate slack --webhook=YOUR_WEBHOOK

This enables:

• Automated standup reminders
• Standup summaries posted to channels
• Blocker alerts for team leads

Step 5: Establish Team Protocols

Technology is only part of the solution. Establish these team protocols:

1. Update Timing: Team members should submit updates at least 15 minutes before standup
2. Blocker Protocol: Anyone reporting a blocker should @mention who they need help from
3. Follow-up Mechanism: Designate who is responsible for tracking blocker resolution
4. Review Cadence: Schedule a bi-weekly review of Microman effectiveness

Step 6: Run Your First Standup

microman standup

For the first few standups, we recommend having team members submit updates during the meeting itself, with the team lead demonstrating the process first.

Step 7: Analyze and Adjust

After two weeks, run the analytics command:

microman analytics --last=14d

This will show:

• Average standup duration
• Common blockers
• Team member participation
• Completion rate of "Next Steps"

Use these insights to refine your process.

Common Pitfalls to Avoid

1. Over-customization: Resist the urge to add too many custom fields
2. Lack of integration: Microman is most powerful when connected to your existing tools
3. Inconsistent usage: Ensure everyone follows the same process
4. Ignoring analytics: The data provides valuable insights for continuous improvement

By following this setup guide, your engineering team can be up and running with Microman in less than an hour, with optimal configurations that promote accountability without micromanagement.