A lot of things happen in a systems development project.

In particular, it is not uncommon for what you are making to not turn out exactly as you had expected.

 

Common situations

Sales (Manager) "Sorry, there was a slight bug here 😃"

Engineer: "That's how it's supposed to work 🤨 (sniff)"

 

...

......

This is so true!

 

You might feel like saying, "Well, it's actually buggy!!!"

 

 

Still, it's dangerous

Even in that case, the conclusion is

The word "bug" is strictly prohibited

It's safe to think of it that way.

 

Why is the word bug banned?

For many engineers

When someone says "It's bugged," it sounds like they're saying "You're not doing your job"

is.

 

Of course, that's not what you meant, right?

I was just pointing out a slight incongruity.

but, The engineer might get angry.

So why does it sound that way?

 

 

it is

The definition of the word bug is There are big differences between sales (managers) and engineers (technicians)

That's why.

 

 

Definition gap

first, A definition often used by sales (managers) is

Bug = something not working as expected

is.

For example, "I wish it would move a little more smoothly, but it's a bit stuck." For sales (managers), this is usually a bug .

 

 

on the other hand, The definition of a bug from the engineer's perspective is usually

A situation where something that was originally decided to be made in a certain way is not going as planned

is.

 

 

How is this different?

 

explanation

As a premise, among engineers (technologists),

1. Things that have been decided as something that must be done and that have been guaranteed to customers, etc.
2. I know it would be better if I could do it, but I haven't promised it to the customer.
3. Now that you mention it, that's true.
4. Maybe you do, but I don't think so.

are clearly separated.

 

 

and, From an engineer's perspective,

A bug is "only" the situation where 1 is not as expected.

refers to.

 

 

In contrast, Sales and managers feel

Step 1,2 and 3 are mandatory. Step 4, OK let's discuss.

This is only natural, as customer satisfaction is directly linked to sales .

 

 

This gap is the difference between sales (manager) vs. It creates a battle between engineers .

 

 

For example, what would the situation be like for a salesperson?

Now imagine this.

 

Suppose The sales person, To the engineer

"You're making all sorts of excuses, but in the end you haven't been able to get any deals, right?"

How would you feel if someone said that to you?

 

No, wait a minute💢

There are a lot of things I can't change myself .

We're doing our best here💢

 

Isn't that how you feel?

 

"I don't want to work with this person anymore!"

Some people may feel that way.

 

That's how powerful the word "bug" is to engineers.

 

 

The true feelings of engineers

Here, I dare If you were to write down what engineers (technologists) really think, I think most of them would say something like this.

• First of all, I've never heard of such a thing (or it's been rejected).
• And no one can know what your "correct answer" is except you.
• Even if you can imagine it, if you have time to realize it, you'll be in trouble if you don't move forward with other things.
  
• And I don't understand why people are angry about that.
• If it's absolutely necessary, please tell your manager and secure the man-hours instead of me.

In a nutshell, this can be summed up as "that's the specification."

 

 

So it's dangerous

So, if you want to proceed with a project without fighting with your engineers,

The word "bug" is strictly prohibited

I strongly recommend that you keep this in mind.

 

So what should we do?

 

Even if you think it's clearly a bug, please say, "I'd like to discuss this 'specification'."

 

 The sales and managers themselves explained the bugs and specifications. Until you can speak at an engineer's level, you should choose the word "specification" instead of "bug ."

 

If an engineer (technologist) thinks "This is definitely a bug,"

We hope that they will take responsibility and say, "Oh, this is a bug. I'll fix it right away."

because, to an engineer, a bug is a bug in reality.

Most of engineers are very honest about the facts .

They just clearly separate bugs from specifications.

and

They are not trying to deny or hide the bug.

 

 

We hope you will develop a great system!

 

If you have any requests such as "I would like to know what has been compiled after the opinions of sales and development have been reconciled," please feel free to contact us using the form below.