This is a report from participating in the study session “UZABASE Meetup#3 Improving Team Productivity”.

Opening LT

There are two factors that reduce team productivity.

1. Over-defining roles

• Vision becomes narrow.
• Becomes individual play, making coordination difficult.

2. Deciding who's responsible

Spending time thinking about responsibility when failures occur is really wasteful.

“Role boundaries should be kept ambiguous, and what needs to be done should be viewed from a bird’s eye perspective.”

• Q) When things are ambiguous, doesn't work load get biased toward specific people, or don't some tasks get picked up by anyone? Are you doing anything special?
• A) Having the team talk for 10 minutes daily, saying things like "I'm having trouble with this," and having real communication made the team work well.

Increase productivity for a happy life

Why emphasize "productivity"?

• Speed is the source of competitiveness
• Time outside work is also important

Really, it’s these two things.

How chatops freed engineers from routine work

• Q) Besides push notifications, are there examples of successfully introducing chatops to non-engineers?
• A)

Trinity GitHub-driven development

So they use ZenHub. I used it before but stopped because page rendering was too slow. I wonder how it compares to Trello?

• Q) I used ZenHub before but found the slow display frustrating. Don't you find it irritating?
• A) We recognize it's slow.

Summary

Uzabase gave the impression of being a company with a good engineering atmosphere.

That’s all from the Gemba.