+1 |
|
DP here. I have to say MCPS occasionally "listens" to what they want to listen and make small but more disastrous refinement. I gave a feedback in one of the Oct. virtual meeting that Region 2 with Wheaton HS was the only region that had real engineering program/curriculum and anyone in that region can apply to. The sample STEM curriculum shared back then only contained two SMCS entry-level engineering courses. Guess what happened? In November, they added interest-based engineering programs to every region, removed the two SMCS entry-level engineering courses, and maintained the exact same budget estimate. They keep on adding or tweaking programs without considering any logistics/staff/transportation/student cohort/etc associated with it. |
Honest question - have you ever had a job? No, a new leader does not just get a blank slate when previous leadership has lied to the community. There's a lengthy trust-building process, inclusive of cleaning house. Taylor has not built trust. He did not clean house, and these sweeping changes have been undertaken in a way that has shocked the community. Take the proposed closing of SSIMS. That had NEVER been on the table and suddenly materialized as a fait accompli in Phase 2 of the so-called "iterative process." If you are going to do something devastating to the community like shut down a walkable neighborhood middle school, there should be extensive community discussion first. |
To the pro-MCPS poster: This. You're patting yourself on the back with this is so-called iterative approach, yet this means this process and the details will not be ready for who knows how long. Did it occur to you that this same very proposal is going on a PR tour, being built into the boundary studies, and the BOE VOTES on this come March 2026. Where else in the real world does a half-baked idea become reality without having at least looked at all the details - staffing, bussing, cost, etc. But for you, it's ok that all of this will be unknown. Bravo. Who cares about 7th graders and younger? |
The description in bold also applies to all of our design team meetings. A waste of everyone's time. |
|
New poster who was also on the design team. I wish I could have those hours back.
And I do not appreciate the scolding tone of staff emails. |
can you all draft a joint letter? At minimum, to ask them to respect community if they want to take people's time without compensating them? |
I am on the design team and would love to see and sign a letter like this. I am tired of MCPS using our names to the Board of Ed pretending that we are part of some real process of community feedback, and that everyone who opposes the way they're doing this are opposed to the regional approach as a whole or afraid of change or an unrealistic perfectionist. Most of us think there is a lot of promise in this model but both the process and the current outcomes are infuriating. If the Board is going to pass this, they should at least understand how deeply resistant and honestly almost hostile Taylor and MCPS staff have been to gathering feedback and considering the opinions of others besides themselves. I'm just a nobody so it doesn't mKe sense for me to start it-- I would suggest that some of the somebodies who know eachother work together on something and then use their networks (which I do not have) to get other design team members onboard-- but I would love to sign something if it's created. |
A bunch of you team members should contact Nicole Asbury at The Washington Post. She just wrote a story about this topic. |
But the initial design was riddled with errors, lacked insight into individual schools and their offerings, and didn’t account for documented demand (or lack thereof) for particular course progressions. MCPS didn’t analyze current programs to identify strengths, they didn't examine their own failures with past programs, and they were resistant to feedback from staff and parents who had experience with both success and programs. This wasn’t a process of improving a solid concept. It’s been a process of deploying multiple sets of massive revisions to deal with the profound design flaws. |
| *experience with both successful and unsuccessful programs. |
| DP - Also, when I hear "iterative" I don't think just iterating on PowerPoint, but actually slowing implementing and observing how things go on the ground and making adjustments as needed. Not launching 97 different programs simultaneously. |
+1 There are many people in addition to the design team members that have spent many hours trying to understand the proposals and their potential impact on our high school cluster and on organizing and advocacy. It's incredibly stressful for our communities to watch CO staff run around proposing crazy things left and right and then having to try to somehow reach them to explain why what they are proposing is crazy. Community members should not have to spend hours and hours trying to address flaws that would never have been there had they been proactive in engaging and working with communities and school staff while developing their proposals. What they are doing is trying to ram through what they want and giving lip service to the people they upset the most. This is an exhausting and frankly abusive process. |
I’m glad you are doing it for your community. I feel the same way and am doing it for mine. |