Bottlenecks within the Organization

In looking over Figure 1-2 "How to read a Network Diagram", it is inevitable that central people tend to be considered "bottlenecks" within the organization if the team members are heavily dependent on them. But we need to keep in mind that, bottlenecks are very good at their profession, but yet are overloaded and busy in their work of line, as Cross mentions. This is true in most organizations and this doesn't mean that they are not connected. Take for example, Paul in the diagram. It is said that his colleagues from Finance, Marketing and Manufacturing come to him, but he never goes to them. He certainly must be well established and holds a great expertise and value to the organization. But what we do not see here in the diagram is where Paul reports to. There is obviously a VP or a President of Finance Department. In a sense, in the organization there is a hierarchy of who reports to whom and that if Paul is considered a bottlneck, then his boss would be considered a bottlneck as well since he would also be occupied with a tremendous amount of work he does. Then this would be a continuous pattern within the organizations.

Identifying Types of Individuals in a Network

We live in an era where social networking plays a vital role in our daily lives, whether it may be personally or professionally. Chapter 5 deals with "Identifying types of Individuals in the Network" by which they are broken into four groups. Central connectors-are generally connectors who represent a direct relationship in the network Boundary spanners-are connectors of a department who connect other departments in the organization.
Information Brokers-are communicators accross subgroups of an informal network.
Peri-pheral people-people who are in need of getting better connected with others. Within the following groups, the author gives us an insight of how managers are assessing peoples position in a network, particularly when they are "Stuck on the Periphery". It is certainly interesting and at the same time true that when individuals join the organization, they find themselves having difficulty of knowing and networking with others. However, the author gives one of the examples, that I have experienced at the personal level while working for an organization. He states that in order to develop connections, it is the best to put individuals with other collegues who are more "networked or experienced". At the time I worked with Raytheon Technical Service, headquarterd in Reston, VA. I was hired as the Help Desk Technicians, not knowing anybody in the company. I found it to be a little difficult to create network, since most of my work was trouble shooting and solving problems over telephone conversation; not to mention being in a cubicle for long hours. At one point, our IT Manager had decided that it would be the best, if he sent one from us (one at a time) to different locations to work with our team-mates and a way to get to know each other; as well as to work on the project during that time. Right away we could tell that our productivity level has dramatically increased and we were able to create even more network with other IT specialist, Engineers, Programmers in which we often were the first ones to know about job openings and other resources. Up to this day, I am well connected with others, both personally and professionally in the organization and believe that it is vital part of my life for continuous network and friendship.

Tryout

Hello Everyone-

I am Benjamin Jazavac, an American University student who will be using blogger as a way to post materials related to my Social and Networking class. With this I certify that all postings will be made by myself and in compliance with the American University conduct code.