Maintaining good mental health check for employees

Mental health is an important part of a healthy workplace. Employees who are struggling with mental health issues can be less productive, miss more days of work, and have a negative impact on the overall morale of the workplace. As a leader, it’s important to recognize the signs of mental health issues and to provide support to your employees.\n\nThe first step to helping your employees maintain good mental health is to create a workplace environment that is supportive and understanding. This means having open conversations about mental health and creating a culture where employees feel comfortable talking about their issues. Additionally, having clear policies in place that provide support for employees who are struggling with mental health issues can be beneficial.\n\nLeaders can also help their employees maintain good mental health by encouraging them to take breaks throughout the day and to practice self-care. Taking regular breaks throughout the day can help employees manage stress levels and reduce the risk of burnout. Additionally, encouraging employees to take part in activities that promote self-care, such as yoga or meditation, can be beneficial.\n\nFinally, leaders should provide resources to employees who are struggling with mental health issues. This could include providing access to mental health services, such as counseling or therapy, or providing access to online resources. Additionally, having an Employee Assistance Program (EAP) in place can be beneficial, as it provides employees with access to confidential mental health services.\n\nMental health is an important part of a healthy workplace, and as a leader, it’s important to recognize the signs of mental health issues and to provide support to your employees. By creating a supportive environment, encouraging employees to take breaks and practice self-care, and providing resources to employees who are struggling with mental health issues, leaders can help their employees maintain good mental health.

The importance of 1:1 meetings between development managers and their reports.

Why are 1:1 meetings important?

One to one meetings are an essential part of management for all companies large or small, they provide a way for managers to connect with their reports. Its always a good idea to prioritize one to ones in our calendars and ensure that there is a regular space that can be allocated for the private conversations.

Together with each member of your team, reserve thirty to sixty minutes once a week or twice a week to talk about the timetable. This will help you stay on track. Do not allow yourself to feel hemmed in by the confines of a conference room; instead, propose taking a break from the office to go for a stroll or grab a cup of coffee.

While some managers like to schedule their one-on-one meetings on a specific day of the week, others prefer to spread out their meetings throughout the week so that they may maintain the highest possible mental presence. One advantage of scheduling meetings on the same day as one another is that it makes it easier to identify connections between the various activities being carried out by your team. Determine whatever method is most effective for you, then construct your timetable so that it returns the most information to your reports.

The one-on-one meeting is the most effective method for managers and the people who report to them to connect on important matters, build a solid connection, and guarantee that employees feel as though they are working toward their goals, both in the workplace and in other aspects of their lives.

However, if you do not have an appropriate framework, agenda, and mindset for the 1:1 encounter, it is possible that it will become just another meeting in your day. Here is our strategic strategy for making the one-on-one meeting the most important meeting you attend, whether you are a manager or an individual contributor.

In 1:1 meetings a manager sits down with an employee for the purpose of having a dialogue that can go in any direction and is planned in advance. The one-on-one meeting, as opposed to the status report or the tactical meeting, is an opportunity for coaching, mentoring, providing perspective, or even just venting. The one-on-one meeting goes beyond merely having an open door policy and instead sets aside time on a consistent cadence for leaders and their teams to engage with one another and communicate.

There isn't just one approach to set up a one-on-one meeting. The emotional requirements of people you manage, the nature of your relationship with the team member, and the degree of experience they have all play a role in determining the most effective method to plan your meetings so that they are productive.

The creation of an environment in which individuals may talk freely about the topics and worries that are on their minds is the most essential component of a productive one-on-one meeting. The employee is the primary focus of these discussions, and their presence is absolutely necessary.


Managers approach to 1:1

Each manager will have their own approach and ability to add their own personality and style to their one to ones. Start your one-on-one meeting with an open-ended question. This lets the most important and important-to-me topics rise to the top. Here are some questions you might try:

How are you feeling? (Open ended to see how the report is feeling, as well as to look for hidden signs in their tone and words; there may be hidden signals to their mental state as well, which may necessitate additional questions and care.)

What did you learn last week / since we last talked? (Another open-ended question that will look for good and bad things they have learned; this may also provide insight into good and bad things they have learned.)

What are you most looking forward to?

What do you worry about the most?


Reports approach to 1:1

Take each meeting with your line manager seriously; this is your dedicated space where you can address concerns and learn about new information. Make notes during the week to remind yourself of topics to discuss and to ensure that your meeting runs smoothly. This is also a place to provide feedback/brag notes, letting your line manager know about the good things you've done so they're visible and not forgotten. If, like me, you are not involved in the day-to-day grunt work with the team, this is an excellent opportunity to let the management know about the excellent work you have been doing.

Another important aspect of this is managing up, where feedback and improvements can be fed back to management to improve processes and highlight any issues that can be identified early.



Installing Angular 11 with MVC 5 (4.7.2)

As part of a recent redesign project at work, we were looking at upgrading the current front end framework to Angular 11 whilst maintaining the much larger .net project in the backend. Despite a lot of searching I didn't manage to find any decent sources or tutorials as to how to do this successfully, In this article I will outline the following topics that will be discussed.

  • Installing Angular 11
  • Adding Angular to MVC 5 project
  • Set up lazy loading loading of components.
  • Recommendations for project folder structure.


Set up MVC 5 (4.7.2) Project

As there are already many tutorials if you really need one out there, set up a new / add a MVC project to your solution. Theres nothing special in this step.



Set up Angular 11 (2+)

Next is to set up Angular inside your new/existing project, likewise there are plenty of tutorials out there so will provide some snapshot scripts.

$ npm install --global @angular/cli
$ ng new angular10-example
$ cd angular10-example

The steps above are to install the angular cli globally, then create via scaffold the new angular project with your desired name.


The next part of the set up was the areas with little tutorial online and took some figuring out.

In the _Layout.cshtml

  • Add the reference to the base href <base href="/"/>

Setting up the bundles

  • After choosing your output directory and running ng build
  • Navigate to your BundleConfig.cs file and add the script bundle, note that with output angular files you cant minimize it again as this will cause the front end to error. So instead of using ScriptBundle use Bundle instead as below.

Setup call between MVC and Angular.

Now in the Index.cshml or what ever area you can to load the Angular app in add the call to <app-root> and the call to the bundles @Scripts.Render("~/bundles/angular"), note that the call to then bundles has to be after the app root.


Set up Lazy loading routing of components

In your main routing module, add a call to load children of your desired component main module example as app-routing-module.ts

Then just ensure that in your component section you have your child routing structure mapped as well