Please enable JavaScript.
Coggle requires JavaScript to display documents.
Central theme: The disconnect within the IT field - Coggle Diagram
Central theme: The disconnect within the IT field
Potential solutions
Potential solutions (most likely to work)
Messaging ability to notify new employees (possibly through email or other forms of communication)
Would let both new people and people who aren't aware of what's going on within the company get a better idea
Requires a change in technology, as the communication changes to be a lot more technology heavy and spaced out (would likely be done over a set of various emails IE)
Create affinity groups
Would make it so that people are able to get used to their own groups and would allow them to integrate into the company a bit better, allowing them to be more cooperative and understand the company's goals better
Changes the process and people needed as it requires different people for the group, and requires a step to change the people each time
Put a lot more effort into integrating employees, especially ones not registered for orientation
Would lead to a difference in that the groups would now be a lot more integrated into the system, making it so that they'd be a lot more willing to care about the other subgroups
Would require changing almost everything, as it not only entirely changes the process but would also require dedicated people for this alongside using technology to integrate new employees more actively.
Chosen solution
Creating affinity groups
Pros:
Not that hard to implement, allowing for another solution with little risk if it doesn't work out.
Makes everyone included
Properly integrates the various employees more effectively, making it so people will be more willing to help other branches
Makes people feel wanted
Raises overall morale
Working as a team provides a wide variety of unique benefits that being alone can't provide
Cons:
Requires getting groups set up
You'll need to ensure each group has a good amount of members
Risk of some people not wanting to join groups
Comparing to other solutions
Very easy to implement with willing participants
Easy to shut down if it doesn't work, little major investment
Simple to implement
Feasible in that it can provide a lot of help and benefits theoretically, and won't have any major downside if it does backfire and doesn't help.
Sources for this idea (working in a group of like-minded people) helping:
https://www.sandler.com/blog/6-benefits-of-teamwork-in-the-workplace/
https://www.cmu.edu/teaching/designteach/design/instructionalstrategies/groupprojects/benefits.html
https://www.skillsyouneed.com/rhubarb/group-work-benefits.html
Relevant facts
Disconnect between IT and other branches
Initiation has a lot of issues that could be the cause of the disconnect
A lot of ideas can't be dealt with since other aspects need to be dealt with first
Key problems
Information Technology group isn't properly engaged with the rest of the company, creating a rift between groups
Exists due to there being a gap between the various industries, causing them to not communicate as clearly.
This has happened for a variety of reasons, but the most infamous one seems to be how they aren't properly shown how the company works, which hurts them when they get in.
Leads to a variety of consequences:
IT group doesn't work with the goals of others efffectively
The company doesn't cooperate as smoothly.
A variety of people are responsible, with the key blame going to the higher ups of the various groups for not fixing the system.
The initiation system struggles to properly represent the country
This problem exists by the program not properly allowing a more refined and thought out "sign-up" system as to cause the struggle.
The consequence is that it leads to the company losing money , but it also impacts the organization by making them not work as well as possible, and affects the IT group by not helping them get integrated properly.
The person responsible is the person who made the system
The initiation system is heavily flawed and has a lot of oversights
Exists since there are issues with the code
Caused by issues that are overlooked when the program was created
Leads to a loss in profit and the IT group being less initiated
Unclear who is directly responsible, but likely the people who designed the imitation system
Stakeholders
Ryan, the employee
Risk of getting fired
Nick, the boss
May not be able to afford all the employees he needs, or could have the company suffer due to a lack of communication
Maggie, another employee
Risk of getting fired
The company
Could lose money
The company shareholders
If profit goes down, stocks and shares will likely be worth less
Investors
With groups not working together, it leads to the issue where the company isn't working effectively, not leading to anything the investors can benefit from
Timeline
Ryan thought about how he could improve orientation
Ryan went to orientation
Ryan had his first day in office and learned that there was a lack of communication between the It field and the other fields
Ryan realizes he needs to help the company branch understand the goals of the other branches
He tries to communicate his ideas with Maggie on how to improve orientation, but she's already thought of most of them.
He learned there are various issues slowing progress.
Staff has limits on the people with each specialty who could sign up for orientation. Made too many people of one group show up but not others.
People would have to randomly cancel their registration, but this did not properly cancel the person's hotel room, forcing them to pay.
IT group not properly engaged.
Nobody in IT to talk to
Ryan goes over the various options he could take in fixing things
He decides on the next path he could take to help fix the issues