Two executives in charge of Google's most turbulent products are leaving this week.
Read the whole story
Read the whole story
I'm an engineer, so I am biased, but I actually think a competent marketing person would absolutely hate the idea of fragmentation (all of the messaging apps) and removing features (the google pay debacle). If it confuses users, marketers should (and usually do) hate it. I think this was either a very bad engineering decision (simplify the apps or make them more single purpose? Who knows) or an MBA optimizing for EBITDA or some other BS.Both of these executive's last had engineering experience decades ago. I do wonder if a lot of the missteps that Google has made around these products are largely related to having the wrong skillset in charge.
I know nothing of what plagued these products development, and I'm completely talking out my ass, but I do think Google would do well to put engineers with more recent engineering experience into these leadership roles, not business/marketing people, if they want their products to launch well.
Google's engineering team is huge, and they have a lot of intelligent developers, and it is always shocking when products shit the bed and are buggy, missing features etc, and I just know that didn't come about as a result of a competent engineer helming the ship, but instead an out-of-touch marketing/business person saying it's good to go.
I'm an engineer, so I am biased, but I actually think a competent marketing person would absolutely hate the idea of fragmentation (all of the messaging apps) and removing features (the google pay debacle). If it confuses users, marketers should (and usually do) hate it. I think this was either a very bad engineering decision (simplify the apps or make them more single purpose? Who knows) or an MBA optimizing for EBITDA or some other BS.Both of these executive's last had engineering experience decades ago. I do wonder if a lot of the missteps that Google has made around these products are largely related to having the wrong skillset in charge.
I know nothing of what plagued these products development, and I'm completely talking out my ass, but I do think Google would do well to put engineers with more recent engineering experience into these leadership roles, not business/marketing people, if they want their products to launch well.
Google's engineering team is huge, and they have a lot of intelligent developers, and it is always shocking when products shit the bed and are buggy, missing features etc, and I just know that didn't come about as a result of a competent engineer helming the ship, but instead an out-of-touch marketing/business person saying it's good to go.
To put it differently, Google pays you to understand their formula.It's been reported that internal promotions are driven by metrics around user count and novelty and "growth".
The decisions are nonsense by normal standards, but they are planned to game/use an internal Google formula for success.
Maintaining a stable product doesn't get much weight, so this is the outcome.
The all mighty algorithm!I'm an engineer, so I am biased, but I actually think a competent marketing person would absolutely hate the idea of fragmentation (all of the messaging apps) and removing features (the google pay debacle). If it confuses users, marketers should (and usually do) hate it. I think this was either a very bad engineering decision (simplify the apps or make them more single purpose? Who knows) or an MBA optimizing for EBITDA or some other BS.Both of these executive's last had engineering experience decades ago. I do wonder if a lot of the missteps that Google has made around these products are largely related to having the wrong skillset in charge.
I know nothing of what plagued these products development, and I'm completely talking out my ass, but I do think Google would do well to put engineers with more recent engineering experience into these leadership roles, not business/marketing people, if they want their products to launch well.
Google's engineering team is huge, and they have a lot of intelligent developers, and it is always shocking when products shit the bed and are buggy, missing features etc, and I just know that didn't come about as a result of a competent engineer helming the ship, but instead an out-of-touch marketing/business person saying it's good to go.
It's been reported that internal promotions are driven by metrics around user count and novelty and "growth".
The decisions are nonsense by normal standards, but they are planned to game/use an internal Google formula for success.
Maintaining a stable product doesn't get much weight, so this is the outcome.
The all mighty algorithm!I'm an engineer, so I am biased, but I actually think a competent marketing person would absolutely hate the idea of fragmentation (all of the messaging apps) and removing features (the google pay debacle). If it confuses users, marketers should (and usually do) hate it. I think this was either a very bad engineering decision (simplify the apps or make them more single purpose? Who knows) or an MBA optimizing for EBITDA or some other BS.Both of these executive's last had engineering experience decades ago. I do wonder if a lot of the missteps that Google has made around these products are largely related to having the wrong skillset in charge.
I know nothing of what plagued these products development, and I'm completely talking out my ass, but I do think Google would do well to put engineers with more recent engineering experience into these leadership roles, not business/marketing people, if they want their products to launch well.
Google's engineering team is huge, and they have a lot of intelligent developers, and it is always shocking when products shit the bed and are buggy, missing features etc, and I just know that didn't come about as a result of a competent engineer helming the ship, but instead an out-of-touch marketing/business person saying it's good to go.
It's been reported that internal promotions are driven by metrics around user count and novelty and "growth".
The decisions are nonsense by normal standards, but they are planned to game/use an internal Google formula for success.
Maintaining a stable product doesn't get much weight, so this is the outcome.
I think the presumption there is that anyone cares if their areas of responsibility were a disjointed mess.Somehow when you are high enough up the corporate food chain, past performance doesn’t seem to matter much when jumping ship. Like if you were looking for a lower level leadership post to fill, would you prefer someone whose prior area of responsibility is a disjointed mess?
Indeed! That Javier guy leaving is nothing, but Google should have showered Mr. Ready with dollar bills until he agreed to remain as head of their payments program.Having the guy in charge of payments named "Bill Ready" is so on the nose I'd think it was a terrible DC comic adaptation.
I look forward to Google Workspace Pay and Google Workspace Chat, which will be consumer products existing in parallel with just plain Google Workspace.
Also, be looking for the launch of Google Meat, their SaaS HR offering!
Indeed! That Javier guy leaving is nothing, but Google should have showered Mr. Ready with dollar bills until he agreed to remain as head of their payments program.Having the guy in charge of payments named "Bill Ready" is so on the nose I'd think it was a terrible DC comic adaptation.
I'm an engineer, so I am biased, but I actually think a competent marketing person would absolutely hate the idea of fragmentation (all of the messaging apps) and removing features (the google pay debacle). If it confuses users, marketers should (and usually do) hate it. I think this was either a very bad engineering decision (simplify the apps or make them more single purpose? Who knows) or an MBA optimizing for EBITDA or some other BS.Both of these executive's last had engineering experience decades ago. I do wonder if a lot of the missteps that Google has made around these products are largely related to having the wrong skillset in charge.
I know nothing of what plagued these products development, and I'm completely talking out my ass, but I do think Google would do well to put engineers with more recent engineering experience into these leadership roles, not business/marketing people, if they want their products to launch well.
Google's engineering team is huge, and they have a lot of intelligent developers, and it is always shocking when products shit the bed and are buggy, missing features etc, and I just know that didn't come about as a result of a competent engineer helming the ship, but instead an out-of-touch marketing/business person saying it's good to go.
It's been reported that internal promotions are driven by metrics around user count and novelty and "growth".
Indeed! That Javier guy leaving is nothing, but Google should have showered Mr. Ready with dollar bills until he agreed to remain as head of their payments program.Having the guy in charge of payments named "Bill Ready" is so on the nose I'd think it was a terrible DC comic adaptation.
When I get an email that says "Bill Ready", I do not want to open it.
*Citation needed*Google has a good product,
Agreed, at least that a competent marketer/marketing team would not allow this out the door (nor the revolving door of rebrands, a la Microsoft's similar strategy).I'm an engineer, so I am biased, but I actually think a competent marketing person would absolutely hate the idea of fragmentation (all of the messaging apps) and removing features (the google pay debacle). If it confuses users, marketers should (and usually do) hate it. I think this was either a very bad engineering decision (simplify the apps or make them more single purpose? Who knows) or an MBA optimizing for EBITDA or some other BS.Both of these executive's last had engineering experience decades ago. I do wonder if a lot of the missteps that Google has made around these products are largely related to having the wrong skillset in charge.
I know nothing of what plagued these products development, and I'm completely talking out my ass, but I do think Google would do well to put engineers with more recent engineering experience into these leadership roles, not business/marketing people, if they want their products to launch well.
Google's engineering team is huge, and they have a lot of intelligent developers, and it is always shocking when products shit the bed and are buggy, missing features etc, and I just know that didn't come about as a result of a competent engineer helming the ship, but instead an out-of-touch marketing/business person saying it's good to go.
Google had a pair of high-ranking executives leave this week. The first was Bill Ready, Google's "President of Commerce, Payments & Next Billion Users,"[…]
Ready was only at Google for two-and-a-half years, where his highest-profile move was presiding over the disastrous rollout of a significant Google Pay revamp.
I've been living under the Apple rock so I am completely clueless when it comes to Android.
If I'm in the US setting up my brand-new phone (Samsung? Pixel? Moto?) running the latest, WTF am I using to pay using my phone? I dont't have to use Google Pay, no? Or do I just tap by credit/debit card on the reader and call it a day?