6 Downsides of Yumemi Inc. (Part 2)
Continuing from last time, I will list the downsides of the system development company I work for, "Yumemi Inc."
Click here for Part 1
Now, let's move on to Part 2.
4. No In-House Services
Our company's work is "creating things together with client companies."
Therefore, we basically have no in-house services.
Some projects are not even publicly disclosed
There are projects that Yumemi does not disclose as part of its portfolio.
So, even if you develop and release something, and it's being advertised on TV, there are times when you can't say, "I'm the one who developed this service!"
Therefore,
"I want to work for a company with in-house services!"
"That's where I find fulfillment!"
↑ If you are that kind of person, I don't think you will behappyworking at Yumemi Inc.
Follow-up
Since you can participate in various clients' projects, you get to experience a wide range of technologies.
For example---
-
Project A
Vue + TypeScript
-
Project B
React + TypeScript
↑ It's fun that the tech stack differs from project to project like this.
"I heard React is more compatible with TypeScript than Vue, but so this is what it's actually like!"
Having moments like that makes for great material to write articles on Qiita or Zenn.
Also, designers and engineers are invited to meetings from the requirements definition stage, and we work together with the clients to refine the requirements, so I feel like I'm working as if I were participating in the development of an in-house service.
There are no situations where you're a 5th or 6th-tier subcontractor wondering, "Why am I developing this feature?" or "What is the client trying to achieve by building this system?" All our projects are direct contracts.
5. Sometimes you can't choose your own project
"At Yumemi, you can choose the projects you participate in!"
That is the policy.
However, during times when there is less work...
PM: "Hey."
PM: "We just landed one new project."
PM: "Yametaro, which project do you want to take?"
Me: "Which one? I mean..."
Me: "There's only one, isn't there!!!"
↑ Things like this have happened too.
Follow-up
Basically, you can choose the projects you are interested in from several available options.
PMs and others will hold project briefing sessions for us at the start.
6. If you do something bold, you might be surprisingly criticized
Yumemi's CEO (Reitch) says...
"It's okay to fail, so let's just try experimental things!"
"In fact, let's praise failure!"
"Let's praise the act of trying!"
↑ I'm pretty sure that's what he said.
I think this is a wonderful way of thinking in itself.
Praise first when someone fails
Suppose an employee tries something 'new, experimental, or bold,' and it ends in failure...
"What are you doing?"
"The way you did X wasn't good."
If it's a company thatcriticizes first, then gradually...
"If I try something and fail, I'll get criticized..."
The atmosphere becomes like that, and
eventually, I think it becomes a company whereno one takes on challenges.
Therefore, I strongly agree with 'Let's praise failure!'
I strongly agree, butI feel the reality doesn't match it.
How does it not match?
Since our company has an 'All-CEO System,' any employee can carry out 'major reforms.'
In fact, there are employees who try to do quite experimental things.
However, at times like that, on Slack and elsewhere...
“There is a risk of making a XX mistake.”
“You should think about it more.”
I see quite a lot of negative opinions like that.
Not suggestions for improvement, but rather just criticism like that.
When I see things like that...
“Wait, I heard that even if you fail, you’ll be praised!?”
“With this kind of attitude, I lose the desire to try experimenting!?”
is what I end up feeling.
Follow-up
Even if the company’s policy is “Go ahead and experiment!”, at the end of the day, everyone’s philosophy and way of thinking are different.
It can’t be helped.
“It’s better not to fail” is a natural feeling, after all.
However, I think, “No matter what anyone says, go ahead and experiment and fail as much as you want!!!”
I don’t think there has ever been anyone who succeeded in innovation without being criticized.
I also don’t think there has ever been anyone who succeeded in innovation without failing.
Even if you are trolled by some clueless, good-for-nothing person,
or conversely, criticized by someone who actually understands,
or criticized by a colleague,
or even denied by someone you respect,
if you think “This is interesting!” or “This should be done!”, then you should just do it.
I believe that innovation only happens beyond that point.
I don’t know for sure, though.
However, having that much obsession while also listening to others' opinions to carry out reforms is incredibly difficult, isn't it...
Summary
The title says “10 things,” but there weren’t even 10.
I’m ending it at 6!
~The End~