Transformation at ING (C): Culture

William R. Kerr; Alexis  Brownell

}
//]]>
</script>
<input type="hidden" name="__VIEWSTATEGENERATOR" id="__VIEWSTATEGENERATOR" value="E39AC016" />
<script type="text/javascript">RegisterSod("sp.core.js", "\u002f_layouts\u002fsp.core.js?rev=7ByNlH\u00252BvcgRJg\u00252BRCctdC0w\u00253D\u00253D");</script><script type="text/javascript">RegisterSod("sp.res.resx", "\u002f_layouts\u002fScriptResx.ashx?culture=en\u00252Dus\u0026name=SP\u00252ERes\u0026rev=b6\u00252FcRx1a6orhAQ\u00252FcF\u00252B0ytQ\u00253D\u00253D");</script><script type="text/javascript">RegisterSod("sp.ui.dialog.js", "\u002f_layouts\u002fsp.ui.dialog.js?rev=Tpcmo1\u00252FSu6R0yewHowDl5g\u00253D\u00253D");RegisterSodDep("sp.ui.dialog.js", "sp.core.js");RegisterSodDep("sp.ui.dialog.js", "sp.res.resx");</script><script type="text/javascript">RegisterSod("core.js", "\u002f_layouts\u002f1033\u002fcore.js?rev=Emb5hNX1RZMNXk9oS82yvA\u00253D\u00253D");</script>
<script type="text/javascript">
//<![CDATA[
var _spFormDigestRefreshInterval = 1440000;window.g_updateFormDigestPageLoaded = new Date(); window.g_updateFormDigestPageLoaded.setDate(window.g_updateFormDigestPageLoaded.getDate() -5);function loadMDN2() { EnsureScript('MDN.js', typeof(loadFilterFn), null); }
function loadMDN1() { ExecuteOrDelayUntilScriptLoaded(loadMDN2, 'sp.ribbon.js'); }
_spBodyOnLoadFunctionNames.push('loadMDN1');//]]>
</script>
<script type="text/javascript">RegisterSod("sp.runtime.js", "\u002f_layouts\u002fsp.runtime.js?rev=IGffcZfunndj0247nOxKVg\u00253D\u00253D");RegisterSodDep("sp.runtime.js", "sp.core.js");RegisterSodDep("sp.runtime.js", "sp.res.resx");</script><script type="text/javascript">RegisterSod("sp.js", "\u002f_layouts\u002fsp.js?rev=\u00252B4ZEyA892P3T0504qi0paw\u00253D\u00253D");RegisterSodDep("sp.js", "sp.core.js");RegisterSodDep("sp.js", "sp.runtime.js");RegisterSodDep("sp.js", "sp.ui.dialog.js");RegisterSodDep("sp.js", "sp.res.resx");</script><script type="text/javascript">RegisterSod("cui.js", "\u002f_layouts\u002fcui.js?rev=OOyJv78CADNBeet\u00252FvTvniQ\u00253D\u00253D");</script><script type="text/javascript">RegisterSod("inplview", "\u002f_layouts\u002finplview.js?rev=WB6Gy8a027aeNCq7koVCUg\u00253D\u00253D");RegisterSodDep("inplview", "core.js");RegisterSodDep("inplview", "sp.js");</script><script type="text/javascript">RegisterSod("ribbon", "\u002f_layouts\u002fsp.ribbon.js?rev=F\u00252BUEJ66rbXzSvpf7nN69wQ\u00253D\u00253D");RegisterSodDep("ribbon", "core.js");RegisterSodDep("ribbon", "sp.core.js");RegisterSodDep("ribbon", "sp.js");RegisterSodDep("ribbon", "cui.js");RegisterSodDep("ribbon", "sp.res.resx");RegisterSodDep("ribbon", "sp.runtime.js");RegisterSodDep("ribbon", "inplview");</script><script type="text/javascript">RegisterSod("sp.ui.policy.resources.resx", "\u002f_layouts\u002fScriptResx.ashx?culture=en\u00252Dus\u0026name=SP\u00252EUI\u00252EPolicy\u00252EResources\u0026rev=YhBHGmUAGyJ3lAgSdE4V\u00252Fw\u00253D\u00253D");</script><script type="text/javascript">RegisterSod("mdn.js", "\u002f_layouts\u002fmdn.js?rev=gwmFFJ2\u00252FfFacqXWAqG\u00252FqKg\u00253D\u00253D");RegisterSodDep("mdn.js", "sp.core.js");RegisterSodDep("mdn.js", "sp.runtime.js");RegisterSodDep("mdn.js", "sp.js");RegisterSodDep("mdn.js", "cui.js");RegisterSodDep("mdn.js", "ribbon");RegisterSodDep("mdn.js", "sp.ui.policy.resources.resx");</script>
<script type="text/javascript">
//<![CDATA[

function _spNavigateHierarchyEx(nodeDiv, dataSourceId, dataPath, url, listInContext, type, additionalQString) {
    SetAdditionalNavigateHierarchyQString(additionalQString);
    g_originalSPNavigateFunc(nodeDiv, dataSourceId, dataPath, url, listInContext, type);
}

g_originalSPNavigateFunc = _spNavigateHierarchy;
_spNavigateHierarchy = _spNavigateHierarchyEx;
var _fV4UI = true;//]]>
</script>
<script type="text/javascript">RegisterSod("msstring.js", "\u002f_layouts\u002f1033\u002fmsstring.js?rev=QtiIcPH3HV7LgVSO7vONFg\u00253D\u00253D");</script><script type="text/javascript">RegisterSod("browserScript", "\u002f_layouts\u002f1033\u002fnon_ie.js?rev=EVTj1bu32\u00252FMla6SDN\u00252FsNTA\u00253D\u00253D");</script>
<script type="text/javascript">
//<![CDATA[
var __wpmExportWarning='This Web Part Page has been personalized. As a result, one or more Web Part properties may contain confidential information. Make sure the properties contain information that is safe for others to read. After exporting this Web Part, view properties in the Web Part description file (.WebPart) by using a text editor such as Microsoft Notepad.';var __wpmCloseProviderWarning='You are about to close this Web Part.  It is currently providing data to other Web Parts, and these connections will be deleted if this Web Part is closed.  To close this Web Part, click OK.  To keep this Web Part, click Cancel.';var __wpmDeleteWarning='You are about to permanently delete this Web Part.  Are you sure you want to do this?  To delete this Web Part, click OK.  To keep this Web Part, click Cancel.';//]]>
</script>
</form>

Go to main content

Supplement | HBS Case Collection | May 2018

Transformation at ING (C): Culture

by William R. Kerr and Alexis Brownell

Abstract

In 2016, ING Group began an overhaul of its company culture, culminating in a code of conduct dubbed "The Orange Code."

Keywords: ING; company culture; cultural change; Change; Organizational Culture; Change Management; Banking Industry; Financial Services Industry; Netherlands;

Language: English

Format: Print

14 pages

Purchase

Citation:

Kerr, William R., and Alexis Brownell. "Transformation at ING (C): Culture." Harvard Business School Supplement 818-121, May 2018.

About the Author

William R. Kerr

Dimitri V. D'Arbeloff - MBA Class of 1955 Professor of Business Administration

Entrepreneurial Management

View Profile »
View Publications »

More from the Author

Teaching Note | HBS Case Collection | September 2019 (Revised October 2019)

Hot Chicken Takeover

William R. Kerr, Manjari Raman and Olivia Hull

Citation:
Kerr, William R., Manjari Raman, and Olivia Hull. "Hot Chicken Takeover." Harvard Business School Teaching Note 820-021, September 2019. (Revised October 2019.) View Details

Cite View Details Purchase Related
Case | HBS Case Collection | September 2019 (Revised October 2019)

Google: To TVC or Not to TVC?

William R. Kerr and Carl Kreitzberg

In late 2018, evidence emerged that many of Google’s temporary help agency workers, vendors, and independent contractors (“TVCs”) were unhappy with the company. TVCs, who reportedly made up 49.95% of Google’s 170,000 person global workforce, had raised concerns of mistreatment, citing instances of pay inequity, social exclusion, and physical endangerment. “Flexible” workers, such as TVCs, were often seen as a key cog for Silicon Valley’s IT companies: they made workforces scalable, they helped firms get access to specialized knowledge for temporary projects, and they boosted innovation by creating “knowledge spillovers” between firms. But, at the same time, many onlookers worried that flexible work arrangements were aggravating social inequality and making more jobs precarious. Google employees, major media outlets, and politicians demanded that the company change its policies on TVCs. One suggestion was that Google convert all of its TVCs to full-time status by early 2020. As tensions reportedly escalated between Google’s workforce and its management team, some began to wonder if Google was still an employer of choice.

Keywords: workforce; independent contractors; labor; talent management; Silicon Valley; google; employee attitude; Employee compensation; employee engagement; future of work; innovation; Innovation and Management; innovation and strategy; inequality; talent acquisition; Labor; Talent and Talent Management; Technological Innovation; Employees; Innovation and Management; Human Resources; Information Technology Industry; United States; San Francisco;

Citation:
Kerr, William R., and Carl Kreitzberg. "Google: To TVC or Not to TVC?" Harvard Business School Case 820-048, September 2019. (Revised October 2019.) View Details

Cite View Details Educators Related
Case | HBS Case Collection | May 2018 (Revised October 2019)

Managing the Future of Work

William R. Kerr, Allison Ciechanover and Jeff Huizinga

By 2019, leaders from the public and private sector had become increasingly anxious about how advanced technologies and aging global populations could affect labor markets, workplaces, and workers’ lives. Some analysts forecasted that hundreds of millions of workers would have their jobs threatened by automation. Questions about how relevant stakeholders (e.g., workers, firms, NGOs) should respond to those threats created a new field of study called the “Future of Work.” Comparing current forecasts to historical episodes of workers getting automated, many commentators wondered “will this time be different?” Despite so much uncertainty on the topic, many leaders concluded that they would need to collaborate across sectors to address many different challenges, such as rapid technological changes and evolving labor markets.

Keywords: Employment; Technological Innovation; Organizational Change and Adaptation; Change Management; Problems and Challenges; Opportunities;

Citation:
Kerr, William R., Allison Ciechanover, and Jeff Huizinga. "Managing the Future of Work." Harvard Business School Case 818-128, May 2018. (Revised October 2019.) View Details

Cite View Details Educators Purchase Related

Faculty & Research

Transformation at ING (C): Culture

Abstract

Citation:

Related Work

About the Author

More from the Author