• Elisabeth_The_Third
  • There is nothing more powerful as an idea whose time has come
  • Los Angeles, United States
  • Offline

Business Blog

December 2, 2008

Trust

It is a greater compliment to be trusted than to be loved.
George Mac Donald


Character                  Wisdom                          Competence
Integrity                 Judgement                    Technical
Maturity                                                      Conceptual
Abundance                                                 Interdependence
Mentality   

                                                 
Almost all the work is done through relationship with people and in organizations. But what is communication like when there is no trust? It is impossible. It is like walking through the minefield. What if your communication is clear and precise, yet there is no trust? You will always be looking for hidden agenda. A lack of trust is the very definition of bad relationship.


The Speed of Trust


What is communication like when there is high trust? It is easy, it is effortless, it is instantaneous. There is nothing as fast as the speed of trust. It is faster then anything you can think about. Trust is the glue of life. It is the glue that holds organizations, cultures and relationship together.


Making and Keeping Promises
Nothing destroys trust faster then making and breaking a promise. Nothing builds and strengthen your trust more than keeping a promise you make.
Never use word promise until you are totally prepared to pay whatever price is to keep it.


Honesty and Integrity
Basketball coach legend Rick Pitino captured the principle of honesty: “Lying makes a problem part of the future; truth makes a problem part of the past.”

Trust is a highs form of motivation. Trust people, and when you do, you give a priceless gift and opportunity to others. The greatest risk of all is the risk of risk-less living.

November 24, 2008

The Laws Of Web Design

A great article - MUST READ - can be found at http://ejoh.zmolklife.com/fs/lowd.html

"A small list of laws concerning web design"

Mitch ’s observation

95 percent of the functionality will take 5% of the time to program, and the other 5 % - that which we call �the exceptions� - takes 95%.

Outline

First Law On System Planning

The Law of Detail

The Laws On Your Client’s Behavior

Hofstadter's Law

Murphy’s Law On Web Design

Wienberg’s Law (general law but applies to web design too)

Emil’s Principles

Emsz' Law of Self Criticism

Golub’s Laws of Computerdom

Glaser’s Law

Mitch's observation

 

 

Tags: Web Design

November 24, 2008

Does-not-exist-in-reality News

Broken banker continues to insist on the reliability of a burned-out bank

translation from http://davydov.blogspot.com/2008/11/blog-post_17.html

Alexei Semonin, the former owner SeverInvestBank, that declared bankrupt last week, convened a press conference «to stop rumors about the reliability of the bank».

«I know that you, journalists, like sensations. However, while not distort the facts. The facts are that SeverInvestBank is one of the most reliable and innovative banks in Russia. We go from the crisis stronger than entered it all the enemies of spite. So make yourself a note. »

After the journalists drew attention to the banker that the bank owed more than five billion rubles, the Central license was revoked, and all property seized, Semonin exploded.

«It is all black PR of unscrupulous competitors who are afraid of us and can not win in the market for fair competition. I do not deny the fact that everything you say takes place; however, it shows that you are not a specialist. Couldn't you call the slogan of our bank? Our slogan, incidentally, «Getting Rich Together». Getting Rich, not losing money. And together, it means that our investors also getting richer. What is the difference, even we cannot pay the debt if we have such a good slogan? Did you think? »

Then, financier hit with critics on the gullibility of people.

«Jornalists, I suggest you better start educating people. After all, our people are too dense. They believe if they ceased to repay deposits, if ATMs do not function, if the Bank property is arested, the bank has a problem. All of this leads to panic... and that panic is dangerous, not ATMs, which stopped issuing money. Why do not you write an article about our logo. Logo, among other things, is blue, a color that makes people calm. Explain to the Russians that if the bank has beautiful logo and slogan, the bank is reliable and it must bear the money. Why pay so much attention to secondary issues such as the inability to get their money back? »

Stood a small pause, Semonin decided to elaborate on the bank loan portfolios, which has led to bankruptcy.

«People criticized us for poor quality of our loan portfolio; asking idiotic qestions like how people with salaries of fifteen thousand, may pay a loan of three hundred thousand. Or why we have such a high percentage of not returning money back. All these questions are posed by people who have no skills of strategic planning.

Let me tell you briefly about the strategy of our bank. We give credit to drug addicts. They are buying cell phones on credit and do not return loans.o Our security services is well aware of this. In fact, they receive 50% of the amount as a rollback. This is not important. We pack these loans and sell them to investors. This is most important. As things now stand, our investors stopped buying our paper because none of our loans are not paid. But this is a temporary situation. Sooner or later, investors accustomed to it and begin anew to buy our paper. Therefore, fundamentally, our position is very strong because we have many practices, how to find drug addicts and insolvent borrowers, we know how to do it better than our competitors, and our competitors are concerned about this fact».

At the end of the press conference , the banker opened his laptop and showed reporters a PowerPoint presentation.

«Have a look at our mission - to become the most innovative and fast-developing Bank in the North-West Russia. Now see graphics. 2007 - 4 offices. 2008 - 400 branches. 2009 - 14000 offices. We are innovative. OUr customers do not stay in line to pay for their apartments and flats, but use online banking. Actually, they do not use online banking yet. But we are already working on technology to connect our users to online banking through television sets Rubin and Sokol. We just push our competitors. This must be emphasized, rather than on the fact that our office is closed, or that we withdrew the license. More importantly,  our financial statements were prepared by the McKinsey consultants ? You think about it when you write an article aoubt our bank. »

After thanking all the journalists for caming to a press conference, banker Semonin asked them to pay hundred rubles for a taxi and promised to meet again with officials «when the bank will open its fourteen thousandth office and all the skeptics will be ashamed». Publishing house "Supid Manager" will monitor bank developments.

 

 

Tags: Fun Bank News

http://www.joelonsoftware.com/articles/fog0000000033.html

The biggest complaint you'll hear from teams that do write specs is that "nobody reads them." When nobody reads specs, the people who write them tend to get a little bit cynical.

The fact that the spec was shelved (unread and unloved) when it was completed makes people feel like it was all a bunch of work for naught.

So. Specs are good, but not if nobody reads them. As a spec-writer, you have to trick people into reading your stuff, and you should also probably make an effort not to cause any already-too-small brains to leak out through eye-sockets.

Tricking people into reading your stuff is usually just a matter of good writing. But it's not fair of me to just say "be a good writer" and leave it at that. Here are four easy rules that you absolutely must follow to make specs that get read.

Rule 1: Be Funny

Rule 2: Writing a spec is like writing code for a brain to execute

Rule 3: Write as simply as possible

Rule 4: Review and reread several times

R ule 5: Templates considered harmful

 

Here are three things to avoid

Don't let the marketing people be program managers. No offense, but I think my readers will agree that good marketing people rarely have a good enough grasp of the technology issues to design products.

Basically, program management is a separate career path. All program managers need to be very technical, but they don't have to be good coders.  Program managers study UI, meet customers, and write specs. They need to get along with a wide variety of people -- from "moron" customers, to irritating hermit programmers who come to work in Star Trek uniforms, to pompous sales guys in $2000 suits. In some ways, program managers are the glue of software teams. Charisma is crucial.

http://www.joelonsoftware.com/articles/fog0000000034.html

When Microsoft started growing seriously in the 1980s, everybody there had read The Mythical Man-Month, one of the classics of software management. The main point of that book was that when you add more programmers to a late project, it gets even later. That's because when you have n programmers on a team, the number of communication paths is n(n-1)/2, which grows at O(n2).

Program manager (project manager) would own the design and the spec for products. Since then, program managers (project managers) gather requirements, figure out what the code is supposed to do, and write the specs. There are usually about 5 programmers for every program manager (project manager); these programmers are responsible for implementing in code what the program manager (project manager) has implemented in the form of a spec.

A program manager (project manager) also needs to coordinate marketing, documentation, testing, localization, and all the other annoying details that programmers shouldn't spend time on. Finally, program managers are supposed to have the "big picture" of the company in mind, while programmers are free to concentrate on getting their bits of code exactly right.

 

 

From http://www.sharenow.com/blog/elisabeth_the_third/post/add/

A functional specification describes how a product will work entirely from the user's perspective. It doesn't care how the thing is implemented. It talks about features. It specifies screens, menus, dialogs, and so on.

A technical specification describes the internal implementation of the program. It talks about data structures, relational database models, choice of programming languages and tools, algorithms, etc.

When you design a product, inside and out, the most important thing is to nail down the user experience. What are the screens, how do they work, what do they do. Later, you worry about how to get from here to there.

Sample of function specification

http://www.joelonsoftware.com/articles/WhatTimeIsIt.html

Here are some of the things I put in every spec.

A disclaimer.

An author. One author.

Scenarios.

Nongoals.

An Overview.

Details, details, details.

Open Issues.

Side notes.

Specs Need To Stay Alive.