Why higher taxes benefit the wealthy

The economic landscape seems pretty clear. The great divide.

a. On the one hand, the wealthy citizen abhors higher taxes, even taxes which are raised to address the increasing Federal and state budget deficits. After all, they worked hard for their money. Why should they sacrifice their gains to help others.

b. On the other hand, we have representatives in the Senate and House of representatives and various other spokespersons for the common man and woman. These voices reason that the wealthy have gained the most so they should be most willing to sacrifice some of their wealth for the common good. Who can better afford these sacrifices than the wealthy?

But what is a sustainable solution to this socio-economic puzzle? Certainly we can all agree that the annual budget deficits of $1 trillion dollars ($1,000 billion dollars) cannot continue indefinitely.

I would propose that diminishing this annual deficit, even if achieved by increased taxes will benefit both those of considerable wealth as well as those of modest income. And here is why.

The mere idea that this annual deficit will diminish is likely to have a massive, positive impact on the economy and the financial markets that reflect economic well-being.  And the wealthy stand to benefit significantly from the growth in both the economy and the markets.

I submit that the benefit of increased income of the wealthy will outweigh the sacrifice that they endure through increased taxes. Consider the following example: Row


 Year 1

 Year 2

 Year 3


Annual income

 $ 250,000

 $ 300,000

 $ 400,000


Incremental tax on investment gains from year 1

 $ 10,000

 $ 30,000


Annual taxes

 $ 74,500

 $ 84,500

 $ 104,500


Tax as a % of total income






Gain over year 1

 $ 50,000

 $ 100,000


Tax increase over year 1

 $ 10,000

 $ 30,000



Net change over year 1

 $ 40,000

 $ 70,000

In this example, in row 1, the wealthy taxpayer experiences a significant increase in capital gains from investments as a result of the lower budget deficit.

In row 2 we see that the taxes increase as well, but not nearly as much as the gains.

But as rows 5, 6, and 7 show, the increase in taxes is far less than the increase in income resulting in a substantial net benefit to the wealthy taxpayer.

This example illustrates that if the increase in taxes will result in a lower Federal deficit, then the wealthy taxpayer actually derives a net benefit from higher taxes.

This puts the wealthy taxpayer and the modest taxpayer on the same side of the increased tax argument.

A reduced Federal deficit, even at the expense of higher taxes,  benefits the wealthy earner and the moderate earner alike.

Why improve the business process?

Over 40 years of work in the business community with an emphasis on business process improvement has given me two important insights:

a. No type of automation or business improvement will occur without the active participation of motivated, creative, imaginative  individuals.

b. These same people  abhor change because change is disorienting.  Change takes us out of our instinctive frame of mind  and requires us to think about what we are doing and why we are doing it.  It also requires us to imagine how our proposed changes will impact others.

Let’s identify the top 11 reasons that continual business process improvement makes sense and is, in fact, a vital part of a dynamic and successful business enterprise. In the spirit of a famous television comedian, we start with reason number 11 and work our way up to reason 1.

–  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –  –

11. You can design your work flow for maximum efficiency.  For example, say a standardized, packaged software solution requires you to go to 5 screens and make 8 clicks to accomplish a particular objective.  If this is something you do often, you can design the system to streamline the activity.  How about one or two clicks to get the job done.

10.  Many of us use two or more software solutions in our daily work.  Often, these solutions require duplication of effort.  They require you to enter information two or more times.    If this is true, it is worthwhile to think about an interface between the two existing solutions.

9.  You and your staff have entered a vast amount of data, often as a by-product of your routine activities.  What is the best way to make use of this data?  How about data mining.  Determine what information can help you make better decisions.  Then go about extracting and working with this data.

8. Sometimes you see all the information you need, but it is not presented in the right sequence.  You cannot, in effect, see the forest for the trees.  Think about whether a different presentation of this information can help you see trends and patterns more clearly.

7. Systems can perform calculations that it would be impossible to do manually.  Some kinds of calculations are not just voluminous, they are hard to do.  Let’s instruct the computer to perform the calculations for us.  Great examples of this are  rate of return calculations, regressions, valuations, or any other types of performance measurement or trend analysis.

6. Another reason to automate the business process is to prevent operational error.  Some procedures in your office involve many steps, either manual or automated.  Let’s automate these steps to save time and to minimize the likelihood of operational error.  Chances are, if your staff needs to perform several steps to accomplish a task, on occasion some those steps will be omitted.

5. A sound business process will provide audit trails for any information that you enter or change.  At all times, you should be able to drill down on a specific number and see all the activity or transactions that have contributed to that number.

4. The key to productivity improvement is delegation.  You need to delegate tasks to your staff so that they will learn and you will be freed up to envision new and better ways to accomplish tasks or use information.  If, for example, you use spreadsheets as the basis of your business process, your staff can help you out, but there is a very high likelihood that they will make mistakes.  And it may take you longer to review their work and find their mistakes than it would take for you to do the work yourself.

3.  We should continually review our business process as it impacts employees, customers, and third parties.  How can we deliver information through the internet to improve the timeliness and reduce the cost of communication.

2.  Of course, use of the internet as a communication tool is a two-way street.  We can also use the internet as a data capture tool.  We can have our customers and clients do our data entry work for us.  As Chase Bank, Lands End, and American Airlines have discovered, our customers are also our data entry clerks.

1. What do all of these business process improvement ideas have in common?  They enable us to elevate ourselves from the operational morass and help to keep our mind clear of minutia.  Let the computer and the process handle that.  We are now free to focus on the creative aspects of our job.  The ultimate business process is one in which we arrive at work each day, turn on our computer, and it tells us what tasks need to be performed today.

No-SQL. The topography of a database

In our previous BLOG on No-SQL databases, we focused on Big Data.  We explored the idea that because of the enormous size of the underlying data, our former notions of data efficiency and order no longer apply.  Rather than spread related data across numerous, normalized tables, we strive to keep related data together.  In doing so, we greatly simplify the task of retrieving and storing data.  When we need it, the data is stored in one complex record in one table.  One read and we have it.

But in simplifying the retrieval and storage of data, we create complexity of another kind.  How do we keep track of data that we formerly parsed out with logical precision to individual tables?

  • Customers can place many orders.
  • The orders can contain many line items.
  • The line items can, in turn represent many products.
  • There are invoices to be sent out
  • Backorders to be dealth with, and
  • payments to be received.

How do we propose to store all of this data in one record? In answering this question, we find that our data takes on an unusual shape or topography.  Each”record” is no longer flat like Kansas.  On the contrary, it has contours, shapes, and texture, like Colorado.

We find that each of our data records are lumpy.  They accommodate all the data necessary to describe the underlying business or information problem.

In No-SQL, tThe records and tables are so different, in fact, that when we refer to them we must use different terms.  We refer to collections rather than tables because the structure of the collections are diverse enough to accommodate many different aspects of one data problem.  And we refer to documents rather than records because a record implies structural uniformity rather than the diversity of information that the No-SQL database can accommodate.

But do not confuse No-SQL documents with a word document or other kind of unstructured computer text files.  These are highly-structured data-rich groupings of information designed expressly to accommodate our high performance data storage and retrieval needs.

In attempting to understand the benefits of No-SQL, we can find a helpful analogy in physics where the conceptual transition from Newtonian physics to Einsteinian physics comes to mind.  In Einsteinian physics, space is no longer Euclidean.  It becomes curved.  And time is no longer purely fixed intervals, it behaves differently depending on the relative speed of the objects in question.

Similarly, in No-SQL we no longer think of documents (formerly records) as uniform in length or field count.  Documents can contain a variety of related information that is stored together to describe our business problem or data problem.

We refer to the topography of the documents (the diverse shape of the records)  in a No-SQL database.  Understanding this topography and knowing that it is dynamic and can be changed over time with relative ease is a powerful concept indeed.

No-SQL. When our logical assumptions become illogical

SQL or Structured Query language has been the prevailing mode of database organization for over 40 years. The fundamental concepts that form the basis of SQL were introduced in the early 1970’s.  And fifteen years later, in the mid 1980’s standards were introduced that enforced uniformity for all SQL database solutions from a wide variety of the most respected and pervasive software vendors in the industry:  IBM, Oracle and Microsoft to name the most prominent.  What more could we ask for?

  • an overwhelmingly logical database structure,
  • accepted by the leaders of our industry,
  • with standard that promote uniformity and compliance across commercial software products.

But beginning in 2006 and more recently, we find two forces emerging that are challenging the leadership, acceptance and viability of  SQL.

The first emerging force is “big data”.  We are beginning to see databases of 500 billion or more records.  These databases span disk storage devices and even span computers themselves.  For the past 40 years, it was reasonable in traditional SQL to make logical connections between related data sets.  For example:

  • An order and the underlying order items are related.
  • The customer and customer payments are related.

But the tables in our databases are beginning to take on sizes that exceed our wildest imagination.  And while the task of joining or connecting these “related” tables seems logically sensible, the practical task of doing so for immense data tables is no longer feasible.

Faced with this dilemma, we begin to question the logical purity of SQL and revisit the most fundamental of our data organization questions and assumptions.  Rather than continually splintering and reassembling the components of a logical data record when needed, why don’t we simply store all related information in one record.

We are finding that the very cornerstone and foundation of database logic is being turned on its head.  As is frequently the case, once we challenge our most fundamental assumptions, absent this foundation, elated ideas also begin to give way.  Things that were previously difficult now become easy.  But the contrary is also true.  Those things which were easy with SQL become more difficult.

In subsequent blogs, we will construct a new logical vision.  We will explore these logical issues, the benefits and costs, as we leave the accepted real of SQL and enter the world of No-SQL.