At the time that the Joint Comprehensive Plan of Action (JCPOA) with Iran was being debated here in Washington, I felt that the terms of the deal were far less consequential than how the United States responded to Iranian regional behavior after a deal was signed. I see the events of the past 12 months as largely having borne out that analysis. While both sides have accused the other of "cheating" on the deal in both letter and spirit, it has so far largely held and neither Tehran nor Washington (nor any of the other signatories) have shown a determination to abrogate the deal or flagrantly circumvent its terms. However, as many of my colleagues have noted, the real frictions have arisen from the U.S. geostrategic response to the deal.

I continue to believe that the Obama administration was ultimately correct that signing the JCPOA was better than any of the realistic alternatives—even if I also continue to believe that a better deal was possible, had the administration handled the negotiations differently. However, its regional approach since then has left a fair amount to be desired:

• The president gratuitously insulted the Saudis and other U.S. allies in his various interviews with Jeff Goldberg of The Atlantic. 
• After several alarming Iranian-Saudi dust-ups, administration officials have none-too-privately condemned Riyadh and excused Tehran in circumstances where both were culpable. 
• Washington has continued to just about ignore all manner of Iranian transgressions from human rights abuses to missile tests, and senior administration officials have turned themselves into metaphorical pretzels to insist that the United States is doing everything it can to assist the Iranian economy. 
• And the overt component of the administration's Syria policy remains stubbornly focused on ISIS, not the Bashar Assad regime or its Iranian allies, while the covert side focused on the regime remains very limited—far smaller than America's traditional Middle Eastern allies have sought. 

To be fair, the administration has been quite supportive of the Gulf Cooperation Council war effort in Yemen—far more so than most Americans realize—but even there, still much less than the Saudis, Emiratis, and other Sunni states would like. 

To be blunt, the perspective of America's traditional Sunni Arab allies (and to some extent, Turkey and Israel) is that they are waging an all-out war against Iran and its (Shiite) allies across the region. They have wanted the United States, their traditional protector, to lead that fight. And they feared that the JCPOA would result in one of two different opposite approaches: either that the United States would use the JCPOA as an excuse to further disengage from the geopolitical competition in the region, or even worse, that Washington would use it to switch sides and join the Iranian coalition. Unfortunately, their reading of events has been that this is precisely what has happened, although they continue to debate whether the United States is merely withdrawing or actively changing sides. And as both Bruce Reidel and I have both stressed, this perception is causing the GCC states to act more aggressively, provoking more crises and worsening proxy warfare with Iran that will inevitably aggravate an already dangerously-unstable Middle East and raises the risk of escalation to something even worse.

U.S. President Barack Obama walks with Saudi King Salman at Erga Palace upon his arrival for a summit meeting in Riyadh, Saudi Arabia April 20, 2016. Photo credit: Reuters/Kevin Lamarque.

Looking to year two

All that said, I wanted to use the first anniversary of the JCPOA to think about where we may be on its second anniversary. By then, we will have a new president. Donald Trump has not laid out anything close to a coherent approach to the Middle East, nor does he have any prior experience with the region, so I do not believe we can say anything reasonable about how he might handle the region if he somehow became president. Hillary Clinton, on the other hand, has had considerable experience with the region—as first lady, senator, and secretary of state—and she and her senior aides have discussed the region to a much greater extent, making it possible to speculate on at least the broad contours of her initial Middle East policy. 

In particular, Clinton has been at pains to emphasize a willingness to commit more resources to deal with the problems of the Middle East and a fervent desire to rebuild the strained ties with America's traditional Middle Eastern allies. From my perspective, that is all to the good because an important (but hardly the only) factor in the chaos consuming the Middle East has been the Obama administration's determination to disengage from the geopolitical events of the region and distance itself from America's traditional allies. The problem here is not that the United States always does the right thing or that our allies are saints. Hardly. It is that the region desperately needs the United States to help it solve the massive problems of state failure and civil war that are simply beyond the capacity of regional actors to handle on their own. The only way to stop our allies from acting aggressively and provocatively is for the United States to lead them in a different, more constructive direction. In the Middle East in particular, you can't beat something with nothing, and while the United States cannot be the only answer to the region's problems, there is no answer to the region's problems without the United States.

My best guess is that our traditional allies will enthusiastically welcome a Hillary Clinton presidency, and the new president will do all that she can to reassure them that she plans to be more engaged, more of a leader, more willing to commit American resources to Middle Eastern problems, more willing to help the region address its problems (and not just the problems that affect the United States directly, like ISIS). I think all of that rhetorical good will and a sense (on both sides) of putting the bad days of Obama behind them will produce a honeymoon period. 

[T]he second anniversary of the JCPOA could prove even more fraught for America and the Middle East than the first.

But I suspect that that honeymoon will come to an end after 6 to 18 months, perhaps beginning with the second anniversary of the JCPOA and occasioned by it. I suspect that at that point, America's traditional allies—the Sunni Arab States, Israel, and Turkey—will begin to look for President Clinton to turn her words into action, and from their perspective, that is probably going to mean doing much more than President Obama. I suspect that they will still want the United States to join and/or lead them in a region-wide war against Iran and its allies. And while I think that a President Clinton will want to do more than President Obama, I see no sign that she is interested in doing that much more. 

Syria is one example. The GCC wants the United States to commit to a strategy that will destroy the Assad regime (and secondarily, eliminate ISIS and the Nusra Front). Clinton has said she was in favor of a beefed-up covert campaign against the Assad regime and that she is in favor of imposing a no-fly zone over the country. If, as president, she enacts both, this would be a much more aggressive policy than Obama's, but as I have written elsewhere, neither is likely to eliminate the Assad regime, let alone stabilize Syria and end the civil war—the two real threats to both the United States and our regional allies (and our European allies). 

Even more to the point, I cannot imagine a Hillary Clinton administration abrogating the JCPOA, imposing significant new economic sanctions on Iran, or otherwise acting in ways that it would fear could provoke Tehran to break the deal, overtly or covertly. That may look to our traditional allies like Washington is trying to remain on the fence, which will infuriate them. After Obama, and after Clinton's rhetoric, they expect the United States to stand openly and resolutely with them. At the very least, such American restraint will place further limits on the willingness of a Clinton administration to adopt the kind of confrontational policy toward Tehran that our regional allies want, and that her rhetoric has led them to expect. 

U.S. Secretary of State Hillary Rodham Clinton (C) speaks with Jordan's Foreign Minister Nasser Judeh (L) and United Arab Emirates Minister of State for Foreign Affairs Anwar Gargash as they participate in the Libya Contact Group family photo at the Emirates Palace Hotel in Abu Dhabi June 9, 2011. Photo credit: Reuters/Susan Walsh.

Reconcile, or agree to disagree?

Let me be clear, I am not suggesting that the United States should adopt the GCC analysis of what is going on in the region wholeheartedly. I think that it overstates Iran's role as the source of the region's problems and so distracts from what I see as the region's real problems—state failure and civil wars—even if the Iranians have played a role in exacerbating both. 

Instead, my intent is simply to highlight that there are some important strategic differences between the United States and its regional allies, differences that are not all Barack Obama's fault but reflect important differences that have emerged between the two sides. If this analysis is correct, then the second anniversary of the JCPOA could prove even more fraught for America and the Middle East than the first. The honeymoon will be over, and both sides may recognize that goodwill and rousing words alone cannot cover fundamental divergences in both our diagnosis of what ails the region and our proposed treatment of those maladies. If that is the case, then both may need to make much bigger adjustments than they currently contemplate. Otherwise, the United States may find that its traditional allies are no longer as willing to follow our lead, and our allies may discover that the United States is no longer interested in leading them on the path they want to follow.

As the income inequality discussion continues to simmer across the country, municipal minimum wage ordinances have become hot topics of conversation in many cities. In January 2016, Seattle will implement its second step-up in the local minimum wage in 9 months, reaching $13 for many employers in the city and edging closer to a $15 an hour minimum that will apply to most firms by 2019. San Francisco will reach a $15 an hour minimum by July 2018. Yet cities as diverse as Birmingham, Chicago, Los Angeles, and Louisville have enacted or proposed similar minimum wage laws. It is too early to discern true impact of these local wage ordinances, but speculation abounds regarding whether or how the higher wage will affect firms and the earnings of low-wage workers.

Less prominent in debate and discussion about the minimum wage is the potential impact that higher minimum wage rates may have for nonprofit organizations. Nonprofits perform many critical functions in our communities—often serving the most at-risk and disadvantaged. Yet, fiscal constraints often place a low ceiling on what many nonprofits can pay frontline staff. As a result, many different types of nonprofit organizations—child care centers, home health care organizations, senior care providers—pay staff at rates near or below the targets set by the recent crop of local minimum wage laws. Our popular image of a minimum wage worker is the teen-age cashier at a drive-through window or the sales clerk at a retail store in the local strip mall, but many workers in these “helping professions” are being paid low wages.

Increases in the minimum wage are occurring at the same time that many nonprofit service organizations are confronted with fixed or declining revenue streams. Facing fiscal pressure, nonprofit service organizations may pursue one or more coping strategies. In addition to reductions in staffing or hours, commonly expected responses, nonprofits may cut back services offered, scale back service areas, or favor clients that can afford higher fees.

Such responses could reduce the amount and quality of the services provided to vulnerable populations. For example, elderly populations on fixed incomes may have fewer options for home care. Working poor parents may find higher child care costs prohibitively expensive. Employment service organizations may find it harder to place hard-to-serve jobseekers in jobs due to more competitive applicant pools.

At the same time, higher minimum wages could have positive consequences for nonprofit staffing and capacity. Higher wages could reduce employee turnover and increase staff morale and productivity. Organizations may not have to grapple with the contradiction of serving low-income persons, but paying modest wages.

The most recent set of wage ordinances take cities to unknown territory. Anticipating potential negative effects, Chicago has exempted individuals in subsidized employment programs from its recent minimum wage ordinance. The city of Seattle has set aside funds to help nonprofits meet the higher local minimum wage, but many nonprofit funding streams are beyond the city’s control and are not seeing similar adjustments.

In the coming years, more research on how local nonprofits are affected by local minimum wage laws needs to occur. We should expect there to be a mix of positive and negative effects within a particular nonprofit organization and across different types of organizations. Nonprofit organizations should be engaged as stakeholders in debates around higher local minimum wages. And, nonprofits should actively engage in research efforts to document the impact of higher wages. In particular, nonprofits should work to compile data that can compare staffing, service delivery, and program outcomes before and after wage laws phase-in. Such data could provide important insight into the impact of local wage ordinances.

We also should be careful not to confuse other challenges confronting the nonprofit sector with the impact of higher minimum wages. For example, private philanthropy to human service nonprofits has failed to keep up with rising need and declining public sector revenue streams in most communities—realities that may pose more serious challenges than minimum wage laws, but ones without an obvious scapegoat.

In the end, ongoing debate around local minimum wage ordinances should provide us with the opportunity to re-examine how we support community-based nonprofits as a society and assess whether that support fits with all that we expect the nonprofit sector to accomplish for children and families in our communities. 

The mayoral election in Baltimore has brought local economic development strategies to the forefront. In a city in which inequality—by income, by race, and between neighborhoods—has increased in the past five years, the candidates have made it clear that more action must be taken to close disparities and improve economic outcomes for all residents. In a podcast segment, I commend the much-needed focus on equity but argue that the mayoral candidates should not lose sight of another critical piece of the equity equation: economic growth. Citing lessons from my recent paper, I outline strategies that Baltimore’s presumptive leaders should pursue—as well as several they should abandon—to place the city’s residents on the path to a more prosperous, equitable future.

Listen to the full podcast segment here: 

May’s jobs gains, released this morning, show that only 38,000 new jobs were added this May, down from an average of 178,000 over the first four months of the year, and the least new jobs added since September 2010.

This year’s monthly job gains and losses can indicate how the economy is doing once they are corrected to account for the pattern we already expect in a process called seasonal adjustment. The approach for this seasonal adjustment that is presently used by the Bureau of Labor Statistics (BLS) puts very heavy weight on the current and last two years of data in assessing what are the typical patterns for each month.

In my paper “Unseasonal Seasonals?” I argue that a longer window should be used to estimate seasonal effects. I found that using a different seasonal filter, known as the 3x9 filter, produces better results and more accurate forecasts by emphasizing more years of data. The 3x9 filter spreads weight over the most recent six years in estimating seasonal patterns, which makes them more stable over time than in the current BLS seasonal adjustment method.

I calculate the month-over-month change in total nonfarm payrolls, seasonally adjusted by the 3x9 filter, for the most recent month. The corresponding data as published by the BLS are shown for comparison purposes. According to the alternative seasonal adjustment, the economy actually lost about 4,000 jobs in May (column Wright SA), compared to the official BLS total of 38,000 gained (column BLS Official).

In addition to seasonal effects, abnormal weather can also affect month-to-month fluctuations in job growth. In my paper “Weather-Adjusting Economic Data” I and my coauthor Michael Boldin implement a statistical methodology for adjusting employment data for the effects of deviations in weather from seasonal norms. This is distinct from seasonal adjustment, which only controls for the normal variation in weather across the year. We use several indicators of weather, including temperature and snowfall.

We calculate that weather in May had a negligible effect on employment, bringing up the total by only 4,000 jobs (column Weather Effect). Our weather-adjusted total, therefore, is 34,000 jobs added for May (column Boldin-Wright SWA). This is not surprising, given that weather in May was in line with seasonal norms.

Unfortunately, neither the alternative seasonal adjustment, nor the weather adjustment, makes todays jobs report any more hopeful. They make little difference and, if anything, make the picture more gloomy.

a. Applies a longer window estimate of seasonal effects (see Wright 2013).
b. Includes seasonal and weather adjustments, where seasonal adjustments are estimated using the BLS window specifications (see Boldin & Wright 2015). The incremental weather effect in the last column is the BLS official number less the SWA number.

June’s jobs gains, released this morning, show that 287,000 new jobs were added in June, an impressive rebound after only 11,000 new jobs were added in May (revised down from from 38,000 at the time of the release).

This year’s monthly job gains and losses can indicate how the economy is doing once they are corrected to account for the pattern we already expect in a process called seasonal adjustment. The approach for this seasonal adjustment that is presently used by the Bureau of Labor Statistics (BLS) puts very heavy weight on the current and last two years of data in assessing what are the typical patterns for each month.

In my paper “Unseasonal Seasonals?” I argue that a longer window should be used to estimate seasonal effects. I found that using a different seasonal filter, known as the 3x9 filter, produces better results and more accurate forecasts by emphasizing more years of data. The 3x9 filter spreads weight over the most recent six years in estimating seasonal patterns, which makes them more stable over time than in the current BLS seasonal adjustment method.

I calculate the month-over-month change in total nonfarm payrolls, seasonally adjusted by the 3x9 filter, for the most recent month. The corresponding data as published by the BLS are shown for comparison purposes. According to the alternative seasonal adjustment, the economy added 286,000 jobs in June (column Wright SA), almost identical to the official BLS total of 287,000 (column BLS Official).

Data updates released today for prior months also reveal some differences between my figure and the official jobs gains from prior months. The official BLS numbers for May were revised down from 38,000 new jobs to a dismal 11,000. My alternative adjustment shows that the economy actually lost 6,000 jobs in May, down from 17,000 jobs gained at the time of the release. [i] The discrepancies between the two series are explained in my paper.

In addition to seasonal effects, abnormal weather can also affect month-to-month fluctuations in job growth. In my paper “Weather-Adjusting Economic Data” I and my coauthor Michael Boldin implement a statistical methodology for adjusting employment data for the effects of deviations in weather from seasonal norms. This is distinct from seasonal adjustment, which only controls for the normal variation in weather across the year. We use several indicators of weather, including temperature and snowfall.

We calculate that weather in June brought up the total by 25,000 jobs (column Weather Effect), but this should be considered a transient effect. Our weather-adjusted total, therefore, is 262,000 jobs added for June (column Boldin-Wright SWA). This is not surprising, given that weather in June was in line with seasonal norms.

It’s good to see the jobs numbers rebounding this month. The May number was somewhat affected by the Verizon strike. Also, it is important to remember that pure sampling error in any one month’s data is large, and that could explain part of the weak employment report for May. Averaging over the last three months, employment is expanding by about 150,000 jobs per month—a healthy pace, although a bit of a step down from last year.

a. Applies a longer window estimate of seasonal effects (see Wright 2013). The June 2015 to May 2016 values in this column have been corrected to remove a coding error that affected the previously reported values.

b. Includes seasonal and weather adjustments, where seasonal adjustments are estimated using the BLS window specifications (see Boldin & Wright 2015). The incremental weather effect in the last column is the BLS official number less the SWA number.

[i] Note that, due to a small coding error, my alternative seasonal adjustment for May, at the time of the release, should have been 17,000 new jobs, not -4,000, as was reported in my previous post. In addition to the underlying data revisions, and correcting for this error, the revised alternative seasonal adjustment for May is -6,000 jobs added (second row of column Wright SA).