Skip to content
Marjan Nikolovski edited this page Apr 19, 2021 · 6 revisions


Starting a new project is always exciting. Everything starts with an idea of a certain product that needs to bring some value. The idea is developed and documented by the product owner and then communicated with the development team that needs to build it.

The development team will go through the docs and there will be some communication going back and forth to understand the details and to align over the deliverable. The project methodology is irrelevant in the sense that all involved parties are speaking a different language which eventually makes it harder to align and understand each other.

I remember during high school, together with my friend, we started developing a tool for managing salaries for one accountant and he wanted to be able to change the system time. Thinking about it and discussing it with the accountant it turned out that he wanted to be able to add a record in the past. This discrepancy in communication, speaking different languages, having a different communication language can impact the decisions that we are making when developing an application.

This brings us to the point, how hard will be to find a common language across different roles? This is where Signals come into play as a concept. Signals align all involved parties by asking the right questions:

  • Who should be able to execute this process?
  • Is this particular person granted to execute the process?
  • What are the preconditions that need to be fulfilled before we execute the process?
  • What are the steps of the process itself?

Once the documentation is delivered to the development team they will be able to map it outright and avoid missing out on the details.

When starting the project, in development terms, we tend to reinvent the wheel, and yet it ends being an ellipse. Every project starts with creating a blank solution, setting up the project hierarchy and boundaries, bringing some code base from previous projects, and trying to glue it out. This means that there isn’t any standardization on how we can effectively run, extend and maintain projects in the longer run. Not to mention when a person needs to join the team or to assist with some other active project in the organization. Fear of the unknown is the boss.

Signals' purpose is to fill the gap in this problem. When starting a project, you will have everything set up for you so you as a developer can focus on the business logic. For both beginners or senior software developers, Signals offers you development practices that will make your professional life easier and more creative.

Marjan Nikolovski CEO, Emit Knowledge