How to build strong workflows with different team environments

Every organization has different internal and external teams they work with in their Noibu workflow. Noibu can be used seamlessly with any combination of roles at play. However, the workflow setup varies depending on the people involved. 


The purpose of building a strong workflow is to reach the goal of having no existing errors in your Funnel view in Noibu. As new errors arise, having a repeatable process in place to resolve new errors is key to building a strong workflow.


The five different workflows we typically see are:

  1. Internal Developer who triages (IDT)
  2. Internal Developer with Internal Product User who triages (IDPU)
  3. External Developer who triages (EDT)
  4. External Developer with Internal Product User who triages (EDIPU)
  5. External Developer with Project Manager (EDPM)


In every Noibu workflow, there are three main roles: the Business User, Product User and Developer. 


The Business User oversees the project from start to finish and is usually focused on key metrics like ROI and conversion. The roles this person typically has include being a VP, Director, Manager of Ecommerce, IT, Marketing, QA, Growth, etc.


The Product User prioritizes errors and assigns errors to developer(s). The roles this person typically will hold include being an Ecommerce Manager, Product Manager, Conversion rate Optimizer, UI/UX Analyst, Business Analyst, QA, etc. 


Developers are the ones who push fixes to resolve the issues at hand with their main concerns being focused on software reliability and performance. They have a range of titles including developer, software developer, engineer, software engineer and QA. An Internal Developer is someone who works at your company, whereas an External Developer is outsourced. 


To optimize your website, you should consistently action and solve errors found in the Funnel. Typically, clients operate on 2-4 week sprints. If that is the case, 2-3 Noibu bugs should be included in each sprint from the funnel. The product user is responsible for ensuring tickets are consistently being actioned.


Below are more detailed explanations of each workflow set-up:


1. Internal Developer who Triages (IDT)


In this situation, the internal developer is the one who triages meaning that they both prioritize and resolve the issues. The developer takes the role of the product user by prioritizing errors found in the Funnel. Since the internal developer is linked closely to the internal side of the business, it can be easier to pass on information to them like customer reports, etc.




2. Internal Developer with Internal Product User who triages (IDPU)


This workflow utilizes the strengths of the Product User as they are the ones who prioritize the errors for the internal developers. The key to having this workflow being executed successfully is by strong communication between these two parties. After the Product User prioritizes the errors, the internal developer then resolves the errors. These two individuals work together to drive ROI and conversion rate increases.




3. External Developer who Triages (EDT)


In this circumstance, the development team is external to your organization. Here, it is the responsibility of the agency developer to prioritize the errors and resolve them. Therefore, the Business User should consistently check in on the project to ensure desired results are achieved and to see project success. 




4. External Developer with Internal Product User who triages (EDIPU)


This workflow is a collaborative effort between the Internal Product User and the External Developer. In this circumstance, the Internal Product User prioritizes the errors and triages them for the External Developer. The Developer’s responsibility is to resolve the errors. Since the Product User is internal and the Developers are external, it is vital that there is consistent communication between the two parties to ensure all errors in the Funnel are eventually resolved. With this workflow, it is beneficial that the Product User is internal because the Business User can easily align their goals, leading to desired project success. 




5. External Developer with Project Manager (EDPM)

In this workflow, both the Project Manager and the Developer are external to the company. This means that for the Business User, the process of prioritizing and resolving is completely outsourced. This means that it is the responsibility of the external Project Manager to prioritize the errors and assign them to the developers to be resolved. 



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Please sign in to leave a comment.