Did Trafalgar set in motion a trajectory for the NY-GOV race? (user search)
       |           

Welcome, Guest. Please login or register.
Did you miss your activation email?
May 24, 2024, 05:16:59 AM
News: Election Simulator 2.0 Released. Senate/Gubernatorial maps, proportional electoral votes, and more - Read more

  Talk Elections
  Other Elections - Analysis and Discussion
  Gubernatorial/State Elections (Moderators: Brittain33, GeorgiaModerate, Gass3268, Virginiá, Gracile)
  Did Trafalgar set in motion a trajectory for the NY-GOV race? (search mode)
Pages: [1]
Author Topic: Did Trafalgar set in motion a trajectory for the NY-GOV race?  (Read 442 times)
ProgressiveModerate
Atlas Icon
*****
Posts: 13,933


« on: November 16, 2022, 06:31:09 PM »

This is an interesting question and I think extends beyond just NY and extends to races like WA-Sen and CO-Sen.

I think if you actually want to be tactical with this strategy, you'd want to release your polls slightly later than Trafalgar did. The influx of close R leaning NY polls started around early September which gave Hochul some time to respond and probably solidified partisanship a bit just now that many saw the race on the map.

I think the bigger way in which polling sort of screwed things up was in the House where Democrats triaged a lot of House races that in hindsight they really shouldn't have. At least Rs wasted their money on WA and CO-Sen lol.
Logged
ProgressiveModerate
Atlas Icon
*****
Posts: 13,933


« Reply #1 on: November 16, 2022, 06:53:36 PM »

This is an interesting question and I think extends beyond just NY and extends to races like WA-Sen and CO-Sen.

I think if you actually want to be tactical with this strategy, you'd want to release your polls slightly later than Trafalgar did. The influx of close R leaning NY polls started around early September which gave Hochul some time to respond and probably solidified partisanship a bit just now that many saw the race on the map.

I think the bigger way in which polling sort of screwed things up was in the House where Democrats triaged a lot of House races that in hindsight they really shouldn't have. At least Rs wasted their money on WA and CO-Sen lol.

Arizona's a good example of this. In normal circumstances, there's no way that O'Halleran would be favored in Arizona 1, especially with it being redrawn to be a bit red, but Democrats really favored protecting incumbents above anything else, so money was spent there. There was also some internal polling that showed O'Halleran to be in much better shape, that turned out to be inaccurate. 

Turns out that the 2nd and 5th were way more competitive, and with more money and hindsight, they could have been Democrat victories. Alas!

Just for reference AZ district numbers changes. O' Halleran is now in district 2 which became a Trump district with redistricting. AZ-01 and 6 were the ones that ended up being close and in hindsight where Dems should've invested more money.

I do agree though one of my biggest annoyances this entire cycle was Dems spending tons of money to protect incumbents, including those who were probably already pretty safe (Greg Stanton in AZ-04) or facing really uphill climbs like (AZ-02). The fact they triaged races like CA-27 in a Biden + 12(!) seat is really angering. In the end, they narrowly won some races where they barely invested like NM-02 and CO-08 but they also narrowly lost quite a lot that were probably winnable.

On the R side, they just seemed like they screwed up a bunch of races with terrible candidates, and wasted too much money in races they were probably never winning than investing it in the places that were most important to winning a House and/or Senate majority. They had less of a pro-incumbent spending bias though, in large part because they didn't have as many vulnerable incumbents to defend.
Logged
Pages: [1]  
Jump to:  


Login with username, password and session length

Terms of Service - DMCA Agent and Policy - Privacy Policy and Cookies

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Page created in 0.027 seconds with 12 queries.