Quotes About Organization

There are organizations that talk a lot about the customer and then completely neglect the people that deal with the customer—the employees. The PC principle is to always treat your employees exactly as you want them to treat your best customers.

You don't need to worry about defining the roles in a way that you will live with for the rest of your life—just consider the week and write down the areas you see yourself spending time in during the next seven days.

SCHEDULING. Now you can look at the week ahead with your goals in mind and schedule time to achieve them.

Management works in the system; Leadership works on the system;

If you want to get something done, give it to a busy man.

PRINCIPLES OF PERSONAL MANAGEMENT Things which matter most must never be at the mercy of things which matter least. GOETHE

Principle-centered leadership is practiced from the inside out on four levels: 1) personal (my relationship with myself); 2) interpersonal (my relationships and interactions with others); 3) managerial (my responsibility to get a job done with others); and 4) organizational (my need to organize people—to recruit them, train them, compensate them, build teams, solve problems, and create aligned structure, strategy, and systems).

And to be effective, that statement has to come from within the bowels of the organization.

Businesses, community groups, organizations of every kind—including families—can be proactive. They can combine the creativity and resourcefulness of proactive individuals to create a proactive culture within the organization.

As I told the manager of the first hotel I visited, I know a lot of companies with impressive mission statements. But there is a real difference, all the difference in the world, in the effectiveness of a mission statement created by everyone involved in the organization and one written by a few top executives behind a mahogany wall.

We need to move beyond time management to life leadership

if you organize your family life to spend even ten or fifteen minutes a morning reading something that connects you with these timeless principles, it's almost guaranteed that you will make better choices during the day—in the family, on the job, in every dimension of life.

Put First Things First).

My own maxim of personal effectiveness is this: Manage from the left; lead from the right.

When I write a book without a writing schedule, it is really a nightmare

A leader continuously communicates the benefits of an ever-changing organization. A leader endorses an organization that is continuously reinventing itself to higher and higher levels of productivity and innovation.

Change will not be apologized for. Why apologize for something that will improve the strength of the organization? Every change is made (every last one of them) for the sole purpose of strengthening the ultimate viability of the organization. That's why you advocate the change. That's why you sell it to your team.

A carefully planned meeting can take a third of the time that an unplanned free-for-all takes.

The dictionary is a perfect example of overalphabetization, with its harsh rules and every little word neatly in place. It almost makes me want to go on a diet of grapes and waste away to nothing.

Levels of Design Design is needed at several different levels of detail in a software system. Some design techniques apply at all levels, and some apply at only one or two. Figure 5-2 illustrates the levels. Figure 5-2. The levels of design in a program. The system (1) is first organized into subsystems (2). The subsystems are further divided into classes (3), and the classes are

Streamline parameter passing. If you're passing a parameter among several routines, that might indicate a need to factor those routines into a class that share the parameter as object data. Streamlining parameter passing isn't a goal, per se, but passing lots of data around suggests that a different class organization might work better.

If a class contains more than about seven data members, consider whether the class should be decomposed into multiple smaller classes (Riel 1996). You might err more toward the high end of 7±2 if the data members are primitive data types like integers and strings, more toward the lower end of 7±2 if the data members are complex objects.

Classes and routines are first and foremost intellectual tools for reducing complexity. If they're not making your job simpler, they're not doing their jobs.

Immature testing organizations tend to have about five clean tests for every dirty test.