Commentary

Bob Evans
Senior VP, Global CIO  

Weighing In On Wal-Mart's Fluid Scheduling

I'm in desperate need of some self-image enhancement therapy after reading some of the feedback from last week's piece about Wal-Mart and its implementation of workforce-scheduling software and my assertion that while some employees will have to adapt to new work schedules that can be fluid or even unpredictable, it's nevertheless an excellent business move by Wal-Mart because it will lead to greater customer value by pegging workforce deployment to store traffic.

I'm in desperate need of some self-image enhancement therapy after reading some of the feedback from last week's piece about Wal-Mart and its implementation of workforce-scheduling software and my assertion that while some employees will have to adapt to new work schedules that can be fluid or even unpredictable, it's nevertheless an excellent business move by Wal-Mart because it will lead to greater customer value by pegging workforce deployment to store traffic.One of the most thoughtful pieces of feedback came from Jay Avitable, a CTO at a financial services company. He extended the discussion way past Wal-Mart and whether it is abusing employees and destroying the social fabric in this country and should be brought under the heel of, oh, maybe Human Rights Watch.

The CTO suggested that what's at play here is an ongoing but quite revolutionary upheaval in the fundamental relationship between employer and employee, and he broke out his theory into one of three classes of worker:


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

"One thing that interests me is the way advancing technology has made the most fundamental aspects of the relationship between 'employer' and 'employee' subject to change. When I first started taking on management responsibilities within the IT department of the financial services company for which I work, the 'worker' model was simple. I had a staff (quite large by today's standards) of software developers, network administrators, and hardware maintainers and fixers.

They were all employees in the traditional sense, mostly salaried, some paid hourly, all with fairly predictable schedules. Fast forward a few decades, and things are quite different. I now seem to pay for three classes of 'workers.' One is very much a 'pay as you go' model.

Specifically, outsourcing and off-shoring specific development projects, where 'pay' is very precisely distributed for work very precisely performed.

The next is the 'nonworker,' that is to say, ASP or SaaS solutions. An increasing amount of the budget is to pay for contracts for services, which ultimately winds up being pay to another company's employees.

The third is a seemingly more traditional 'employer and employee' relationship, but perhaps not. These are the several key employees, salaried, who are in our employ due to their advanced technical skills, their demonstrated ability to craft solutions to complex problems, and their proven track record in managing crises. They represent a 'brain trust' of sorts, paid more for their potential than for their minute-by-minute tangible contributions.

While that was a long-winded statement, my point and question is whether or not we are headed toward an economy where a much larger fraction of the workforce (not just IT and knowledge workers) may be subject to the kind of radical change that I have experienced in my little (IT and software) world over the last 25 years?"

Do you see this same type of stratification emerging? If so, is it a good thing or a bad thing?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links