Sometimes the output you get isn't quiet what you are looking for. Here is an example.
"My machine worked great this morning and started to slow down this afternoon."
So you go the machine and run:
Get-Process
You get a lot of information that could probably be better laid out for your quick troubleshooting. This is where select and sort are your friends.
select is an alias for Select-Object
sort is an alias for Sort-Object
First lets try:
Get-Process | Get-Member
This returns all the properties we have to choose from. Remember in PowerShell you are working with actual objects and that allows for a lot of properties and methods.
For now we will select name, starttime, and cpu:
Get-Process | select name, starttime, cpu
It still needs cleaned up so let's sort it:
Get-Process | select name, starttime, cpu | sort cpu
Better, but I don't really care about the processes using hardly any resources so we are going to flip the results by doing:
Get-Process | select name, starttime, cpu | sort cpu -Descending
Now with a quick glance we can see the biggest resource hogs and what time they started. Using select and sort can get you the preferred layout for your specific taste and purpose at the moment. Remember to use gm or Get-Member to find out what object properties are available to select from.

What will do what you need to do? This is the exact question that the Get-Command cmdlet answers. Try it. Open PowerShell and type:
Get-Command *process*

Put it in practice(hit enter at the end of each line and learn from watching the results):
Get-Command *process*
Get-Process *notepad*
notepad.exe
Get-Process *notepad*
Get-Process *notepad* | Stop-Process
First you get the commands. Next you use a command to get a result (or in our case, no result until notepad is open. Finally you use the results to cause an administrative action by piping from one command and resulting object to another command.
Now, go have fun and see what other commands you can discover!

Persistence: firm or obstinate continuance in a course of action in spite of difficulty or opposition.

If you are going to learn PowerShell; If you are going to be a PowerShell professional; You need to persist. There are going to be challenges and you will hate results and get frustrated at times. Learn to get over it and push through. I want you to succeed. In fact, pretty much the entire PowerShell community wants you to succeed and will gladly weight in and help you with those challenges at PowerShell.org. Go ahead and say a bad word if you need to. Then ask for help and attack the issue again, and again, and again. You can do it, others have. They did because they were persistent. You will do it to, if you persist.

Don't give into temptation and close out that console and lean on the GUI. Go ahead and open the GUI to get work done if time is of the essence. Leave the console open and go back to it to figure it out. Your future self thanks you.