Building a remote balanced work culture for the tech team

A. Communication should be async

Faster, quicker, and async messages

Examples of predefined status at org-level

No to quick-call; Yes to quick-share culture

  • Instead of quick calls, we believe in the quick sharing of relevant information that contains enough historical context.
  • We focus on detailed documented descriptions across tools/platforms. Our communication tools are integrated to streamline information flow without any redundancy.
  • Jira has shared discussions related to the tasks in the comment section.
  • Gitlab is integrated with Jira, to sync tickets with PR merge status.
  • Notion has organized brain-dumps of tech & design discussions and is a great platform for documenting Product Requirement Documents (PRDs) as well.
  • Zoom records walkthroughs, KT sessions, tech talks for future reference.
  • Figma contains designs & discussions related to design.
Examples of collaboration tools

B. WorkFlow should be decoupled across the team

The three independent cycles are:

Development cycle

  • Backlog grooming with a soft assignment to developers
  • Sprint planning happens in a gap of at least 2 days to give developers time to estimate with high confidence
  • Weekly Demo happens at the end of the dev sprint-cycle, for features that need to be released

QA cycle

  • Perform sanity and regression test
  • Report P0/blocker bugs; that need to be fixed on priority

Release cycle

  • The release cycle is independent of the entire dev-cycle. All QA-passed features are packaged and taken ahead for release in a separate cycle.
  • PM suggests if they need a feature flag toggle for the passed feature for safety reasons.
  • Release and gather feedback to share with the team.

Sprint Specific Roles

C. Meetings should be limited and planned

a. 15 min daily stand-up

b. Brainstorming and planning

c. P0 critical incident

d. Team bonding

  • Culture-Vulture: Don’t forget to watch the teaser video at the end of this post.
  • and at pod-level

Learnings and Takeaway

  • There is no need for constant check-ups with high-frequency calls
  • Meeting time is limited with defined agenda.
  • There is a comfortable time to figure out estimation and scalable design.
  • The process’s health metrics give enough visibility, that org can focus on the overall goals rather than each minute detail.
  • Most importantly, we get our fun, bonding, and game time without cutting any process calls.

And Presenting to you, memories of Culture-Vulture Season 2




Code, arts, process and aspirations. co-Founded GreedyGame | IIT Ropar. Found at

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Arink Verma

Arink Verma

Code, arts, process and aspirations. co-Founded GreedyGame | IIT Ropar. Found at

More from Medium

The what and how of Strigo’s engineering team

Managing a Remote Team? Stop Counting Hours, Start Measuring Outcomes Instead

What Managers Want: Visibility & Synthesis

3 Simple Ways Small Businesses Can Offer Employee Mentorships