#teams

Posts mentioning hashtag #teams

Below are all the posts — topics as well as replies — that mention the hashtag #teams.

Mention #teams in your post to continue the discussion!

Working at WellMed clinic

I have been laid off after more than 20 years as a physician. It was a huge shock, with no warning—just an invitation to a Teams meeting! Inhumane! On the other hand, it was a relief after working nonstop in a horrible, toxic environment and wondering every day how much longer I could tolerate it. If you still work at Optum/WellMed clinic-leave!—do yourself a favor and don’t waste your time waiting for the next layoff.


Teams and One Drive

Anyone else find Teams to be not very user-friendly and a bit disorganized and chaotic? I spent far too much time having to look for conversations or clear out notifications.. it’s just a mess. Thought I would get used to it, but it’s been long enough and still painful.

And I like being able to share documents on OneDrive, but it’s also so disorganized. People share their documents with me and now I have 400 documents to sort through looking for mine.. and then I’m told you can set up folders, but apparently we don’t have all the features yet and they don’t know who has them and who doesn’t or when we’ll get them. But on top of that, sometimes the documents just won’t open, and I have to log out and restart Teams just as I kick off a call and attempt to share documents. It just su-ks all the way around and I have no idea how anyone was sold on this platform considering how non-user-friendly it is so far.


Rough Estimate : The Message is very clear from Earnings Report

Smaller Agile teams - This means more flattening of organization with high-level individual contributors oversee the team. So Directors/Snr Directors/VP's and SVP's will be high targets as mentioned in this forum earlier. Executives might be forced to take technical roles. Directors/Managers with minimal number of reports beware.

High cost centers like Bay area, East coast is going to be affected more. Expecting around 2500 -3500 people to be cut. India around 1500 - 3000 people. All the pending members in legacy products, FMW products working in California will be major targets.

Lots of low profile developers, freshers will be cut down to make Org lean and clean. Yes recent college grads might need to brush up their leetcode skills. Visa holders from Bay area better start looking around...

Overall expect something in 5000-8000 count. Get ready folks


Will customer support survive?

Does anybody know if the customer support teams will survive these layoffs and if so, which regions are most likely to be safe?

I have heard multiple rumors and it‘s not looking promising. My manager in support keeps telling me everything will be okay, only if I start my shifts early and finish them late, then it will increase my chances of survival.

Is my manager taking advantage of me?


Last week I did not come into the office but worked from home all week. I didn't tell my manager either. Friday afternoon I got a email from HR

about a Tuesday morning Teams meeting they want to do with me and that I do not need to be in the office for this meeting. I have been thinking if they caught me or not. In any given week I may see my Ford manager once if at all when we pass each other in the hallway. Manager is away from our group a lot saying they have a lot of meetings to attend to in other buildings.
I'm not sure yet if I will do Tuesday's morning meeting with HR at my home or go into the office an do it there.


Teams

Heard a comment the other day that implied they are tracking people teams activity, green, yellow and red. This person also said if you don’t sign on to teams they have a report for that. Any truth? All these reports I can’t keep track of what they are tracking. We need a weekly tracking report of what they are tracking so we can track ourselves.
Great now I feel like I should go running.


Let's look at Testing teams next!!

AT&T needs to look at the various test teams. They seem to have the testing being done by contractors, but the employees, since RTO, are now located time zones away and unable to manage them. The testing should be collocated with the engineering teams and be accomplished with our employees, instead of wasting money on contractors that don’t have any skin in the game and couldn’t care less what happens with AT&T. With the current moves that are happening they should move employees from the FirstNet, IoT, and development teams to Redmond, where the majority of testing is being done.


On Teams

I know it's way above my pay grade but this treatise on teams provides the bottom up view of how Fidelity Teams can be organized. In an ironic power/knowledge asymmetry, I, a low low developer on the front line who has no voice, posses the knowledge that the higher-ups would never know. For example, when it comes to which middle managers to cut, I know exactly who's coasting, who's contributing, who's busy kissing the as--s and who's envisioning... A "who in your report chain you would cut?" secret ballot offered to the frontline associates would work if the anonynimity is guranteed and the trust of the upper management is there.

So I can't be specific, instead I provide general principles here which the higher-ups may consider in the up-coming squad to team mass restructing. Please chime in as your feedback will be incorporated and the whole thing will be provided as my comments for the next Pulse Survey. For our voices to be heard, Please be thoughful and constructive and refain from whining or hate.

(1) Team Nature

Fidelity (actually any enterprise) teams can be categorized along two dimensions:

  • What does the team offer (product vs service). Product teams build (dev), service teams operate (ops).
  • The context in which the team functions (general purpose vs domain specific). Data extraction load and transformation (ETL) is general purpose, automatic understanding of scanned PDFs is domain specific. Phone reps in the call center is general purpose, relationship management with institutional clients is domain specific...

Some example teams in each of the four resulting quadrants are provided below:

  • General purpose product team. The team which builds FidCentral or MyAccess. The team which builds the Snowflake data uploading tool...
  • Domain specific product team. The team which builds automated tools to deploy AI Models. The team which builds automatic tools to extract information out of scanned user submitted PDF documents...
  • General purpose service team. Phone reps who answer generic customer questions. Vendor database administrators.
  • Domain specific service team. The team who provisions load balanced top level URL with vendor products such as AVI or F5. The team who manages digital certificates lifecycle with vendor product such as Venafi(?).

(2) Team Leadership

  • Product Team leaders must be technical with engineering qualification and experiences. This in essence is the "engineering driven culture" in Meta and google. MBA's and humanitiy majors with only project management experiences aren't qualified (this is why AWS su-ks innovation and culture-wise).
  • Domain Specific Product Team leaders must further posses the domain specific qualifications and experiences.
  • Service Team leaders can be less technical and more manegerial, such as MBA's and project managers. In many areas, these managerial kind of leaders are needed more than technical ones.

(3) Team Compensation

  • Product team should be compensated more than service team
  • Domain specific teams should be compensated more than general purpose teams

(4) Team Assessement

  • All teams must be assessed with clearly defined metrics. Both service and product have industry standard metrics: Daily Active Users (DAU), Monthly Active Users (MAU), Net Promotion Scores (NPC)...
  • Apply process improvement methodology such as Six Sigma's DMAIC to improve service team metrics

(5) Team Diversity

While MAGA's h1b hate can be extreme, Fidelity Tech's widespread 100% single identity teams are inexcuseably extreme. It's only fair to recall "diversity" in current anti-DEI environment to counteract the extreme over-representation:

  • No single enthinity represents more than 75% of any (tech) team.

What do I missed? What do I get it wrong? Thanks.


Teams Outsourced?

If this forum is a reflection of layoffs, it almost appears IT have been decimated by layoffs much more than other teams. Can I ask which IT teams have definitively been outsourced? Also, which other teams have had meaningful layoffs? Doesn’t seem to be that many outside Operations.


Duplicate Teams

Any tea on what may happen with some of the duplicate teams that are being merged (SD & insert legacy paramount brand here)? Marketing everywhere, MTV/Skydance TV, animation, legal, etc.). Do you think they will finally be merged properly with some grand plan explained to the company?


Direction less leadership

Many of the impacted employees are rehired as contractors and silently offering them to full-time.
Many teams have no projects no work they were enjoying the paychecks with no revenue coming from those teams. Heavy favoritism and lobbying going on which teams to retain and teams to be notified to retire. No place for High performers. Junk and people who dont know basics are driving projects they will eventually fail