Search

Advertisement

Jacob Misiorowski Struggles in Start Against Cubs Despite Brewers' Victory

Advertisement

On Wednesday, September 2, Jacob Misiorowski took the mound at Wrigley Field, where he faced off against the Chicago Cubs. In a performance that will likely be remembered for its struggles, the Milwaukee Brewers' young ace threw 92 pitches over four innings, allowing five earned runs and recording only 12 outs. Despite Misiorowski's difficulties, the Brewers managed to secure a 9-5 victory, which may overshadow his individual performance.

This outing marked a significant moment for Misiorowski, as the five earned runs he allowed tied his career high. His previous worst came during a game on July 2, 2025, against the New York Mets, where he also surrendered five runs in just 3⅔ innings during what was only his fourth start in the major leagues. While the result is concerning, the underlying reasons for his struggles in this game warrant a closer examination.

One might instinctively attribute Misiorowski's performance to fatigue, especially considering the narrative surrounding his workload this season. However, a look at his velocity readings tells a different story. On this particular night, his fastball averaged an impressive 100.9 mph, slightly above his season average of 100.6 mph. Throughout the game, he consistently registered fastball velocities of 100.9, 101.0, and 100.5 mph, even reaching a peak of 102.4 mph. With five pitches clocked at 102 mph or higher, it was clear that he was not suffering from a tired arm.

The crux of the issue lay in Misiorowski's pitch selection. He utilized his fastball only 48% of the time, a stark decline from his typical usage rate of 64%. Instead, he leaned heavily on his cutter, throwing it 36% of the time, nearly triple his usual 14%. Additionally, when he did throw his fastball, he struggled to find the strike zone, resulting in four walks. Despite generating 13 swinging strikes and recording five strikeouts, it was evident that his approach was not aligned with his usual strategy.

This shift in pitching strategy is noteworthy, especially considering Misiorowski's previous outings. In a game against the Atlanta Braves on August 21, he had also leaned more on his offspeed pitches, which led to concerns about potential fatigue. Following that game, Brewers manager Pat Murphy acknowledged that fatigue could be a factor. Misiorowski himself commented on the weariness that comes with the late summer months, noting that the body tends to feel tired as the season progresses.

At just 24 years old, Misiorowski is in his first full season in the majors and has already accumulated 155 innings pitched, surpassing his total from the previous year, which included both major and minor league appearances. With a month left in the season, he is on pace to break Ben Sheets' single-season franchise record of 264 strikeouts, but the Brewers must navigate his increasing workload carefully. The team had previously considered limiting his outings due to concerns about fatigue but ultimately reverted to allowing him to pitch every five days without restrictions.

Misiorowski's rookie season has been a rollercoaster, with an impressive debut that included five no-hit innings and an All-Star selection shortly thereafter. However, the second half of the season has been more challenging, as evidenced by his 5.89 ERA over his last nine starts, culminating in the five-run outing against the Mets that mirrored his struggles against the Cubs.

Looking ahead, the Brewers face a critical decision regarding Misiorowski's usage. If he returns to his normal fastball usage in his next start, it may indicate that Wednesday's outing was an anomaly. However, if he continues to favor his cutter and struggles to find the strike zone, it could signal deeper issues that the team must address. As October approaches, the Brewers must carefully manage the workload of their young pitcher while keeping an eye on their playoff aspirations.

Source: Yahoo Sports

Advertisement

Comments (0)

Be the first to write a comment.

Leave a Comment