When you're developing a project, it's very common to do it with a team. When doing so, you can find a beautiful multiverse that makes everything and everyone fit perfectly, and within every universe, there's chaos and order.

Simply put: The more organized your team is, the better! When you have many individuals with incredible abilities, there’s always room for a little chaos. However, that's the beauty of finding the perfect balance. You can structure your team based on what they do best. So our first question is: What do we mean by  “Multiverse”? Let's put it this way: Imagine  your office  like a gaming area where the better the internet stability and speed, the better each device communicates, and the better the gaming experience becomes.

When working with teams, we have the same scenario. Still, in our case, communication acts as the internet, which is vital for ensuring the project’s roots and enhancing a good working environment.

Depicting a team as a multiverse is fascinating! Unique individuals with different points of view who are aware of the following:

  • Obstacles and challenges to overcome.
  • How to address those challenges.
  • What other stars do we rely on in our multiverse?
  • What sequence should the solutions be implemented in?

And a lengthy "among other things" follows.

The following  example is based on a software development team.

We typically find the following "universes" in projects of this nature:

  • Project managers and/or Scrum Masters.
  • UX/UI designers.
  • Backend Programmers.
  • Front End Developers.
  • Back End Developers.
  • QA (yes, they are part of the team since they will tell us if the project goes according to their request).

The individual who makes up each of these universes have a very different point of view, as you have indeed  observed (or will observe) in your experience working on projects. For this reason, communication is essential in organizing the foundations that will determine the future of DX (Development Experience), effort, time, scalability, and tolerance of our project.

So… How can we provide the best experience?

Similar to how we've been looking for other universes or planets that sustain life. We have to admit that our multiverses exist.

We are free to say "Hello," and we need to be ready to hear back from the exterior universe.

This means that when planning, proposing and executing tasks, we must consider the other universes since each of them observes, plans, relies on, and executes differently.

Here are some examples of these viewpoints based on this example:


When building the design for this UX/UI example, you may have asked yourself the following questions:

  • What color schemes are possible when using color psychology?
  • How should the components appear?
  • How will it appear on a phone, a tablet, a computer, etc.?
  • Which typeface should I use?
  • With this core arrangement, would the customer be able to comprehend the app's flow?
  • Will this component be scalable and realistic for the Front End team?
  • Will the client or user comprehend how to operate this program and how it works?

Front End

If you are a Front End developer , you undoubtedly understand how reliant  we become on the other "universes". This does not mean that their link is more or less significant; rather, it helps clarify questions like:

  • Can I accept 0 or 1000 elements in a neat and scalable manner without  warping?
  • What  data structure will the backend employ to enable the view to print this data?
  • Is my animation performing as well as it potentially can?
  • What library or framework should I employ?
  • I've discovered that the current design cannot  display data on a particular  screen. Can I use my proposal?
  • How will I communicate data between reusable parts?
  • Will I use a storybook to record the components?
  • Exactly how can I create that form step-by-step?
  • Is it possible for me to center that div?
  • How will the user be informed if the request contains a mistake?
  • Which file format will I use for my icons, photos, and other files?
  • SEO: Dynamic or Static?

And more questions like these…

Back End

The backend is the backbone of the data, so the following questions will often be made:

  • If the software will have validation, should it use a token for security
  • Relational or non-relational, that is the question.
  • REST or GraphQL.
  • Who exactly could read, modify, or add data?
  • What data structure will my endpoint return, and how will that help the front End?
  • Will I use API versioning?
  • Laravel or NodeJS (or can I use another)?
  • In case of an error, how will I return my response?
  • How do I calculate this data in real-time without overloading the server?
  • What service will we employ to back up the data and store it?

Among other possible considerations…


You have probably seen these memes on the internet, but the truth is that the finished product would not be as good without them.

In the same example of our design, you may find yourself asking questions like:

  • Does the expected flow of this page exist?
  • Is the load time what you would expect?
  • Does the form meet validation and function as it should?
  • Does this product convey security when I utilize it?
  • Will testing of this feature be possible?

You must appreciate the QA Team for ensuring that our code functions properly and alerting us to any bugs, among many other things.

Scrum Master  and/or  Product Manager

The one in charge of serving as an interface between the Client and Teams, and the one who's aware of the Client's demands and observations, as well as the Project's status and Task Estimates and Pending Tasks.

  • In this sprint, is it possible to create tasks?
  • Will I be required to provide anything for the team, or will there be inquiries on customer requests?
  • Who will be given these tasks, and why?
  • Since this team member is overworked, I must give this duty to someone else to maintain balance.
  • Which tasks will continue into the following sprint?
  • What bugs did QA or the developers find, and what is their current order of priority?
  • Now that the sprint is over, what can we do to make the next one better?

We can complete 3 to 5 user stories per sprint, according to the average of the sprints. And now we may estimate more precisely there! We received a change request from the client, thus in order to avoid overworking the team, we must share a time estimate.

There are more doubts, and actions that help the team to move forward with the project


As we can see, the most critical aspect of a multiverse like this is communication, therefore don't be afraid to question the other universes about your assignment, changes you'd like to make, recommendations, any delays or advancements, or anything else that can hinder progress. We will be able to make decisions more quickly as a result, encounter fewer disagreements, and, most importantly, advance in a thoughtful way with our work.

Even if you are experiencing issues with your computer or the internet, or if you have found refactors or libraries that can help the project even if they are optional . The goal is to express it, request  feedback, then wait for it.

Even if your proposal is not from your universe, you may support others and be grateful. By doing this  your work will also be more comfortable. This will allow us to end the day calmer and happier, in addition to being more productive and having the greatest quality in the result all thanks to finding balance within the multiverse of our project.