# data[].attributes.headline
Better to have OPS support 24* 7. So that people will  be unblocked and productive.

# data[].attributes.subject
Better to have OPS support 24* 7. So that people will  be unblocked and productive.

# data[].attributes.headline
No proper tools provided in order to increase teams efficiency in-spite  of asking many times and providing specs.

# data[].attributes.subject
No proper tools provided in order to increase teams efficiency in-spite  of asking many times and providing specs.

# data[].attributes.body
We barely did what was required (update sections of the site, add some new features, ...), but there wasn't new flashy things, things that engage new users

# data[].attributes.headline
First time doing student user research to better inform our work 

# data[].attributes.subject
First time doing student user research to better inform our work 

# data[].attributes.body
I'd rather hear "this is gonna be a problem, let's try to work together to figure out how to solve this" instead of upper management pretending that everything is always great and every problem is an opportunity in disguise.

# data[].attributes.headline
I love Jon Chen. He’s a great person and designer. 

# data[].attributes.subject
I love Jon Chen. He’s a great person and designer. 

# data[].attributes.headline
Being asked to give input on a strategic decision immediately after being presented the plan. That kind of work should be 1:1, not in a 10 person meeting.

# data[].attributes.subject
Being asked to give input on a strategic decision immediately after being presented the plan. That kind of work should be 1:1, not in a 10 person meeting.

# data[].attributes.headline
This exercise seems futile because decisions are made from Top down in Netdragon so management here doesnt really have as much say as they should

# data[].attributes.subject
This exercise seems futile because decisions are made from Top down in Netdragon so management here doesnt really have as much say as they should

# data[].attributes.body
Even though I receive a lot of positive affirmation and validation from people I work with directly, it does not feel acknowledged or recognized by the company/"powers that be"

# data[].attributes.headline
The culture is rotten. Co-workers have more negative topics to discuss rather then being excited and motivated to be here. 

# data[].attributes.subject
The culture is rotten. Co-workers have more negative topics to discuss rather then being excited and motivated to be here. 

# data[].attributes.headline
We need a content strategist -- someone to help make copy consistent across the platform

# data[].attributes.subject
We need a content strategist -- someone to help make copy consistent across the platform

# data[].attributes.headline
Shipping products that were not fully tested or validated by cross-functional teams

# data[].attributes.subject
Shipping products that were not fully tested or validated by cross-functional teams

# data[].attributes.headline
Lack of communication of product roadmap

# data[].attributes.subject
Lack of communication of product roadmap

# data[].attributes.body
Finding out that we are planning to work on something after being asked to figure out what to work on

# data[].attributes.headline
Working from home feels more productive. ❤️

# data[].attributes.subject
Working from home feels more productive. ❤️

# data[].attributes.body
Love, love, love it.

# data[].attributes.headline
Working on projects that are based on what people think are problems vs. on collected data or real evidence

# data[].attributes.subject
Working on projects that are based on what people think are problems vs. on collected data or real evidence

# data[].attributes.body
M-team openly promotes work-life balance in meetings, but often pushes people to work late and start early.

# data[].attributes.headline
Projects are scoped so tightly before problem alignment occurs, there's no room to solve the real problems

# data[].attributes.subject
Projects are scoped so tightly before problem alignment occurs, there's no room to solve the real problems

# data[].attributes.body
No bonuses or even market rate increments. Each review cycle ends with effect what so ever.

# data[].attributes.body
So hard to do creative/collaborative work on a whiteboard when working virtually

# data[].attributes.body
Working from home and not being able to see people face to face

# data[].attributes.body
Trying to collaborate w/ china team who isn't allowed to access any user data

# data[].attributes.headline
Except medical no perks, benefits, allowances, 401k matching, stocks.

# data[].attributes.subject
Except medical no perks, benefits, allowances, 401k matching, stocks.

# data[].attributes.headline
No quality control. The bar for building products is low 

# data[].attributes.subject
No quality control. The bar for building products is low 

# data[].attributes.body
Please stop firing them

# data[].attributes.body
Continue w/ Bandaid solutions built off of a poor foundation

# data[].attributes.headline
Pushing the features out half baked and experimenting  of user responses

# data[].attributes.subject
Pushing the features out half baked and experimenting  of user responses

# data[].attributes.headline
We often killed a project after 1-3 weeks to revive it months later

# data[].attributes.subject
We often killed a project after 1-3 weeks to revive it months later

# data[].attributes.body
Kicking off projects by deciding on a solution instead of aligning on a problem

# data[].attributes.body
Working on low impact projects

# data[].attributes.body
Lack of motivation because there is no bonus/promotion/raise.

# data[].attributes.headline
Remote has been great besides the late meetings with no clear goal objectives or outcomes. 

# data[].attributes.subject
Remote has been great besides the late meetings with no clear goal objectives or outcomes. 

# data[].attributes.headline
PRD project metrics that are defined based on the solution vs. based on the overall company strategy

# data[].attributes.subject
PRD project metrics that are defined based on the solution vs. based on the overall company strategy

# data[].attributes.body
I'm never going back to an office.

# data[].attributes.headline
Lack of clear alignment on the project goal and a metric that is tied to overall company strategy

# data[].attributes.subject
Lack of clear alignment on the project goal and a metric that is tied to overall company strategy

# data[].attributes.body
Things that usually work for creating an great office culture doesn't translate to good remote culture

# data[].attributes.body
Implementing 80/20 Rule: 80 percent for features and 20 for tech debt was a very good idea that was also embraced by the China team.

# data[].attributes.body
Amazing! Built to help teachers and reduce their workloads, rather than adding more things to their plate.

# data[].attributes.headline
people are very respectful and answers questions when you have them

# data[].attributes.subject
people are very respectful and answers questions when you have them

# data[].attributes.headline
Not enough people to execute on projects

# data[].attributes.subject
Not enough people to execute on projects

# data[].attributes.body
No job security. Thinking about when we will be replaced by ND employees all the time.

# data[].attributes.headline
User research that was not used or ignored

# data[].attributes.subject
User research that was not used or ignored

# data[].attributes.body
Major change in how teams are organized: engineering, BUs, marketing, etc.

# data[].attributes.headline
onboarding was pretty good, loved the "yearbook" I got ahead of time to see people and get an idea of who was who

# data[].attributes.subject
onboarding was pretty good, loved the "yearbook" I got ahead of time to see people and get an idea of who was who

# data[].attributes.headline
Lot of scope to improve Project planning. No proper scoping and directions. Last min changes and rushes.

# data[].attributes.subject
Lot of scope to improve Project planning. No proper scoping and directions. Last min changes and rushes.

# data[].attributes.body
Edmodo spends a lot of time in meetings because there are no clear agendas, takeaways or note taking. Theres not a lot clear decisions made or next steps.

# data[].attributes.headline
Coordination and Understanding with parent company and even though teams leads are here in SM office we have minimum control on their activity.Team members are moved to different projects or work without consulting with leads. Impacting roadmaps and putting features in jeopardy.

# data[].attributes.subject
Coordination and Understanding with parent company and even though teams leads are here in SM office we have minimum control on their activity.Team members are moved to different projects or work without consulting with leads. Impacting roadmaps and putting features in jeopardy.

# data[].attributes.body
Changing directions, plans, and product scope all too often.

# data[].attributes.body
A lot of longtime employees exiting the company, both voluntary and involuntary.

# data[].attributes.body
Working remotely worked for my team,  it didn't slow us down.

Looking forward to continuing wfh in 2021.

# data[].attributes.headline
no investment to strategy, research or data

# data[].attributes.subject
no investment to strategy, research or data

# data[].attributes.body
Data/research doesn't lead or guide what we do or build.

# data[].attributes.body
There are a lot of in product features that were shipped and then just left to wither.

A lot of product areas were created quickly, shipped, and then seemingly dropped. Few items in the product are maintained and cultivated through a true lifecycle, meaure of success. and then improvements.

Stream
Hashtags
Most search features
Message
Folders

# data[].attributes.headline
The bug bounty program process did  not work and is horribly backed up regarding responses back to reporters and actually fixing high priority issues on our website. It seems this program does not warrant importance enough to be prioritized and has been ignored. It sends a message to me that edmodo / engineering does not really care about some major (and minor) issues on our site and doesn’t care about keeping the researchers happy.. I just don’t get it....Also it seems like support’s needs for tools that we need for helping our users never get fixed or built. These things don’t seem important to the powers at edmodo.

# data[].attributes.subject
The bug bounty program process did  not work and is horribly backed up regarding responses back to reporters and actually fixing high priority issues on our website. It seems this program does not warrant importance enough to be prioritized and has been ignored. It sends a message to me that edmodo / engineering does not really care about some major (and minor) issues on our site and doesn’t care about keeping the researchers happy.. I just don’t get it....Also it seems like support’s needs for tools that we need for helping our users never get fixed or built. These things don’t seem important to the powers at edmodo.

# data[].attributes.body
Inconsistency in which teams made use of existing opportunities for alignment/staying updated (e.g. Support team always attends cross-functional meetings and Product Forums, while Implementation/Sales did not)

# data[].attributes.body
Sounds like: Ask Mo(lester)

# data[].attributes.body
We keep hearing how the other shoe already dropped, but more and more people keep getting laid off; this has lead to an environment where it's really hard to get motivated and a lot of people are working under the assumption that ND is just waiting for the right time to replace them.

# data[].attributes.headline
Processes get a little convoluted at times.  not every understands process

# data[].attributes.subject
Processes get a little convoluted at times.  not every understands process

# data[].attributes.body
Fires are being put out people are working hard and not seeing any rewards.

# data[].attributes.body
Pressure to build things one-off for a very specific client. The team has to think through longer term scenarios and how we might
scale.

# data[].attributes.headline
Opportunity to do generative research that helps identify problem areas and map out product strategy moving forward (Admin User Journey & Admin Needs & Goals)

# data[].attributes.subject
Opportunity to do generative research that helps identify problem areas and map out product strategy moving forward (Admin User Journey & Admin Needs & Goals)

# data[].attributes.headline
We have to book some time to update old parts of the application.

# data[].attributes.subject
We have to book some time to update old parts of the application.

# data[].attributes.headline
Need to work with more outside partners/vendors to implement products quickly that are proven.  (Requires LTI, API's to do this)

# data[].attributes.subject
Need to work with more outside partners/vendors to implement products quickly that are proven.  (Requires LTI, API's to do this)

# data[].attributes.body
M team seems disconnected with what happens on the ground. The lack of adherence to policies for respecting peoples time offs and non work hours.

# data[].attributes.body
We lost benefits faster than getting any single addition in compensation when started WFH,,,even though our personal expenses went up for supporting WFH successfully.

# data[].attributes.headline
Coming together as a company for the pandemic and racial injustice

# data[].attributes.subject
Coming together as a company for the pandemic and racial injustice

# data[].attributes.headline
Limited visibility into enterprise decision making

# data[].attributes.subject
Limited visibility into enterprise decision making

# data[].attributes.body
Enterprise priorities seem to be JIT (just in time) and lack overall vision. We tend to hear, react and adjust over and over. The process for which customer feedback leads to roadmap is unclear which makes it difficult for the products teams to build sustainable solutions.

# data[].attributes.headline
We should have a holistic approach on the core product rather than Client based approach.

# data[].attributes.subject
We should have a holistic approach on the core product rather than Client based approach.

# data[].attributes.body
Ex- Removing sign up for entire Egypt to privilege MoE

# data[].attributes.headline
Too many places to go to find items (Confluence, Jira, Airfocus, Trello, google docs, etc.)

# data[].attributes.subject
Too many places to go to find items (Confluence, Jira, Airfocus, Trello, google docs, etc.)

# data[].attributes.body
I have heard multiple managers question the importance of research's role in product or diminishing Jean's findings.

# data[].attributes.body
The promise of a new data and A/B testing tool never realized

# data[].attributes.headline
No goal or vision of leading in any direction. 

# data[].attributes.subject
No goal or vision of leading in any direction. 

# data[].attributes.body
Same we do it all approach

# data[].attributes.body
We really need to focus more on culture and mission, as these are top two things people identify with and want to work for, along with great colleagues.

Not doing a good job of retaining employees. On engineering side, we are losing amazing engineers because of the culture.

# data[].attributes.headline
Unsure of product roadmap is supporting long term company vision

# data[].attributes.subject
Unsure of product roadmap is supporting long term company vision

# data[].attributes.headline
Teams getting getting multiple instructions on the priorities of the projects  (US and China) and getting confused and teams bonding falling apart.

# data[].attributes.subject
Teams getting getting multiple instructions on the priorities of the projects  (US and China) and getting confused and teams bonding falling apart.

# data[].attributes.headline
communication has been good, teams work well together and are open with giving opinions and discussing ideas

# data[].attributes.subject
communication has been good, teams work well together and are open with giving opinions and discussing ideas

# data[].attributes.body
We consistently acknowledge that working too fast on too many things is not ideal. We've seen the negative impact - incomplete features, bugs, etc. We're releasing features with zero follow up.

# data[].attributes.body
Lack of communication with data team
Enterprise coming up with last minute high priority data requests
Lack of focus on what kind of data we collect and how we use it for future plans

# data[].attributes.body
People got fired in middle of the fire storm and remaining team members had to do alot of heavy-lift to work with inexperienced team members and train them on the go with very heavy deliverables in short time.

# data[].attributes.headline
Need a time window to book meetings and a time window to don't allow meetings.

# data[].attributes.subject
Need a time window to book meetings and a time window to don't allow meetings.

# data[].attributes.headline
Made some improvements to PRD crafting process

# data[].attributes.subject
Made some improvements to PRD crafting process

# data[].attributes.body
Closer collaboration w/ cross functional partners, better defined user problems, better alignment on project goals and metrics

# data[].attributes.headline
Balancing client expectations against cost

# data[].attributes.subject
Balancing client expectations against cost

# data[].attributes.body
We've done a lot of work for Egypt MoE, costing a lot in staff and site resources. They keep requesting more unique features, but have we actually received any money? And if we have, are we actually making money considering the huge investment on our side?

# data[].attributes.body
2020 was the year of the ship without thought or long-term strategy

# data[].attributes.body
Still not sure what industry we're trying to fit into, what solution we offer, who we offer it to, etc.

# data[].attributes.body
Process of putting items into Enterprise Product pipeline was inflexible and not fully thought-out. Standards for what items qualify to be added seemed inconsistent / lacked supporting data

# data[].attributes.body
There were too many chefs in the kitchen, leading to delays in decision-making and execution.

# data[].attributes.body
Not enough engineering to resources to pursing these goals

# data[].attributes.body
There's a lot of confusing with moneys coming from Egypt1/Egypt2 initiatives. I wish China execs were more transparent regarding the dates and the actual revenue recognized. It's also odd to US culture for an initiative to start w/o signing a proper contract, but I was told that it's a custom for Asian markets which still strikes me as something that is risky and might adversely affect the team morale if the potential client pulls out at the end.

# data[].attributes.headline
Need a complete vision - when doing projects we are very tactical but don't think holistically where the product should go and have that idea to work towards

# data[].attributes.subject
Need a complete vision - when doing projects we are very tactical but don't think holistically where the product should go and have that idea to work towards

# data[].attributes.body
Tested out several different user research methods: rolling research sessions, RITE studies, Maze unmoderated usability tests

# data[].attributes.body
Criteria for successful project completion and moving on

# data[].attributes.headline
Edmodo Identity Crisis = Doing too much with little resources

# data[].attributes.subject
Edmodo Identity Crisis = Doing too much with little resources

# data[].attributes.body
Are we a consumer product? Enterprise product? Frankly we only have enough resources to do one of these and as a result, we come up with half-baked solutions and our users are the ones who pay for it

# data[].attributes.body
This is something we promised but never came to fruition. Most of our metrics are top level and when we need deeper product metrics it's too hard or not possible.

# data[].attributes.headline
Hard deadlines and no proper planning for resources and time . Teams had to work lengthy hours and its not sustainable.

# data[].attributes.subject
Hard deadlines and no proper planning for resources and time . Teams had to work lengthy hours and its not sustainable.

# data[].attributes.body
The Team was able to pull up the socks when needed to deliver the Large ent. projects/features with stringent timelines, simply like pulling the miracles.