Understanding titles, roles, and role designations

At LinkORB we are not concerned with titles. We are, however, focused on roles and responsibilities. Everyone at LinkORB has at least one role such as software developer, product manager, technical writer, project owner, designer, customer support, and many more. Some people have multiple roles!

The purpose of this guide is to explain common role terminology at LinkORB. Additionally, it will share how role designations like senior or lead indicate additional responsibilities with respect to fellow team members. Finally, given the cross-functional nature of project owners at LinkORB, their responsiblities are described as well.

Here we go!

Team member

Everyone is a team member! Generally speaking, team members are responsible to complete tasks as assigned by a project owner or their team lead. Everyone at LinkORB is a team member and everyone has assigned tasks 😆.

Senior team member

Some team members are designated as senior to reflect a larger scope of responsibilities and greater institutional knowledge. Senior team members often assist in the on-boarding of new team members. Senior team members may have access to system permissions not available to all team members.

Project owner

Project owners are responsible for key task workflow steps such as:

  • Backlog grooming (task definition, prioritization)
  • Task assignment
  • Validation of acceptance criteria
  • Task closure and archiving

Additionally, project owners provide weekly project level updates, while all team members provide task level updates.

In some projects, a project manager may assist a project owner with key workflow steps.

Team lead

While group decision making is preferred and suggestions from all team members are encouraged, team leads have ultimate responsibility for decisions when multiple options or judgement-based decisions are required.

Additionally, team leads act as stewards for all the members of their team. As a steward, team leads are responsible for preparing and conducting periodic check-ins with team members to discuss what’s going well and potential areas of growth. Team leads play an important role in our badge system as well.

Notably, one team lead can act as a steward for another team lead. For example, the software development team lead is currently the lead and steward for the technical writing team lead.

Team leads often have access to information and system permissions not available to all team members.

Hopefully you’ve found this information interesting and useful for further understanding working at LinkORB. Thanks for reading!