Modules

Often, uncertainty is the reason why people don't draw attention to a problem for a long time, even if they know about it. Or they don't propose a change, because they tell themselves that someone has already thought of it.

The available model of organization, and especially organization, is suitable for making it easy for people to draw attention. The more people in a company know where to look for products, for example, the more they can point out what would be useful to change. No sophisticated tool is needed for this.

Step 1: I have an idea

Excellent! Bring it on. In the company information, open the company model and product overview
Select the product for which you have an idea. It may not be just a product, but perhaps a manufacturing process, or even a purchased product
Open the detail - you almost certainly can't do anything about it, that's fine. But you can send it to the owner notice with your idea.

Step 2: I got an idea from a colleague

The idea in the notice will certainly not get lost. It's on your main desk, so you'll see it as soon as you open AyMINE. And if you're not working with it on a daily basis (that's a shame), it will come in your mail with a link.

From the notice, you can open the detail of the product or other record it relates to.

When you think about the notice that came in:

Be sure to reply to whoever sent you the notice. He can see that you've already read the message, but answering is polite.
You know best yourself - because it's your product - whether the notice points to a problem, or it's worth noting the idea in the request and processing it in the project. Or just explaining to the recipient that things are different than they thought.
You can easily create both the problem and the request directly from your desk. On the alert, you use the trace button and select what to create. The newly created problem or request will be automatically linked to the product it concerns.

Why use the alert

When someone has an idea, it does not mean that they know correctly whether it is a mistake, a meaningful change, or there are reasonable reasons why things are the way they are. It is the job of the product owner to decide how to approach the idea. Therefore, the person who has the idea sends the alert, but does not directly create, for example, a problem. The problem would fall into the statistics, so it might bother someone, but mainly it is more laborious to cancel the problems - you need to state the reason, and it will probably get checked during an internal audit.

Unlike an email, the idea does not fit. With a product, it is visible and seen, for example, by the manager, who may ask why the idea was not processed. When you send the same thing in an email, it can end up unresolved, stuck in a pile of more urgent things. A product's notification isn't lost, even if it accidentally changes who takes care of it. Internal emails, on the other hand, are one of the least popular communications and the most frequently missed message. It's therefore a good idea to avoid them and use notice, discussion or notes on records.