Skip to main content

Sociology - Iran's democracy


Let's get into business... Iran has a democracy.

People must understand that democracy is a psychological and sociological phenomenon, It is a state of mind that makes you listen to objections, accept diversities in opinions and choices.

Democracy is an iteration process, It has a trail-error process, and it takes time to maintain and improve.

Democracy is alive. Like all natural phenomenon, Democracy, progresses. The process is like evolution.

No country in the world has a pure democracy. And all are moving toward one by trail-error method, by decisions they make ... (by the way what is pure democracy any way?!)

If we observe the history of Iran, We may be able to see the trend of Iran, toward her values and dreams, is totally natural.

Iran was monarchy for thousands of years, 103 years ago First Iran's Constitution has been created and till 1979 Iran was still a monarchy. Since 1979 revolution for democracy and freedom(Iranian revolution against Pahlavi Monarchy), Iran went through a very tough time:
  • Post revolution period : Everybody knows how difficult it is to control a country after revolution.
  • At the same period of Post-Revolution Period, Iraq attacked Iran and both countries were engaged in war for 8 years (1980-1988)
  • Since then, many countries directly/indirectly put economical and sociological pressures on Iran.
In such a condition, Iran had to control and maintain her democracy too and She did it very well from my point of view.

This year election is a proof to this claim. Candidates for the first time, started to propose their team and plans. They debate about each others plan, and they have economical, political, and sociological team of experts. This means progress!

To be Continued ...


Post a Comment

Popular posts from this blog

Escalate, Escalate, Escalate!

What is escalation at organizations? Is it a way to solve problems? Is it a way to report things? Is it a way to put more pressure? Is it a CYA technique? What is it? How do you use it at your organization? How other colleagues of yours use escalation? Really, think about it and observe.

At IT service companies, leadership measures the performance of IT Help Desk by number of escalated work items over a period of time. The less escalation the better. The reasons are simple:

It is cheaper for companies if an IT Help Desk Specialist resolves an issue than an experienced technical specialist at one or two level higher. This is simple math, one gets $X and the other get $X*2And when client gets result fast, he/she will be happier. So, less escalation equals happier client in IT Services. Client raise an issue, IT Help Desk Specialist resolve it, BOOM, Next!

At organizations, It is amazing (sadly) to see how much lower level managers escalate problems, that they and their fellows can resol…

Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle

I was thinking what the title of this blog post could be, I had couple of options to select from and decided to use a title that uses Disciplined Agile (DA 2.0) Lifecycle. Other options for titles were: Moving From Scrum to KanbanFrom High Performing Scrum Teams to Hyper Performing Kanban  The bottom line is that at some point you may want to move away from Time boxes to a flow of work and service oriented teams and improve performance and throughput without massive and sudden organisational change.  As always, I only share my experience and this may not apply to all situations, context is important. 
Another reason that I selected “Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle” as the title, was that for many it is a question mark how to navigate through DAD life cycles. and I think this blog post could be one of the ways to navigate. 
Context: A Delivery Team started with Type A Scrum with 2 weeks Sprints. After a while, they deploy their …

New Organisational Model For Project Based Companies

Elliot Goldratt suggested a Strategy Tree for project based companies. While that may work for some companies, it will not work for knowledge based workers or Software Development Companies, or Digital Agencies. On the other hand traditional resource planning and resource allocation is also not effective despite all the effort one put into it to make it less of a command and control model - Here I assume we know who are knowledge workers and how their productivity works, Peter Drucker has a fantastic article about Knowledge Workers that I highly recommend you to read, if you have not read it yet: http://www.forschungsnetzwerk.at/downloadpub/knowledge_workers_the_biggest_challenge.pdf
Also, it has been proven that stable teams work better together on long term projects in software development. However, almost majority of software development companies or digital agencies break teams and reassemble them based on new projects or clients. This creates unnecessary complication and waste w…